/**
* Factory for the core structure of a suite
* @template {object} [U = Record<string,never>]
* @param {import('./internal').State<U>} state
* @returns {import('./internal').Context<U>}
*/functioncontext(state){return{tests:[],before:[],after:[],bEach:[],aEach:[],only:[],skipped:0,state,};}
Interesting, but can it do the heavy lifting ts does? I.e. generating a type containing all possible property paths for a nested object, i.e. like this?
With that setup it is now possible to only perform static type analysis on demand. In this case it's used to arrive at "well formed JavaScript" while keeping the source under developer control.
That said you can arrive at a similar TS workflow with vite. esbuild transforms TS "blazingly fast" without doing any type checking. So you can worry about tests first, types second.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Aww... no generics or mapped types? :>
Preact compat
Interesting, but can it do the heavy lifting ts does? I.e. generating a type containing all possible property paths for a nested object, i.e. like this?
Basically the types live in a TypeScript declaration file so it's just TypeScript.
Clean separation between type space (TypeScript) and value space (JavaScript).
With that setup it is now possible to only perform static type analysis on demand. In this case it's used to arrive at "well formed JavaScript" while keeping the source under developer control.
That said you can arrive at a similar TS workflow with vite. esbuild transforms TS "blazingly fast" without doing any type checking. So you can worry about tests first, types second.