You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my case there's tsimp implementation of TS runtime which works like under NodeJS hood and allow to run TS-code natively via node --import functionality.
Current approach to run TS code is strict to predefined set of libraries which is bummer — needs to set up separate testing environment which is not matching to project runtime.
Motivation
It's more like DX-impovement since there's not only ts-node or esbuild is runtimes but many others (ie. tsimp, swc);
Newer implementations of TS runtimes runs usually faster;
Testing environment runtime will match project runtime.
Example
No response
Pitch
It's just healthy competition to let more freedom especially when NodeJS testing assertions works fine (with own quirks but not in runtime topic).
The text was updated successfully, but these errors were encountered:
🚀 Feature Proposal
In my case there's
tsimp
implementation of TS runtime which works like under NodeJS hood and allow to run TS-code natively vianode --import
functionality.Current approach to run TS code is strict to predefined set of libraries which is bummer — needs to set up separate testing environment which is not matching to project runtime.
Motivation
ts-node
oresbuild
is runtimes but many others (ie.tsimp
,swc
);Example
No response
Pitch
It's just healthy competition to let more freedom especially when NodeJS testing assertions works fine (with own quirks but not in runtime topic).
The text was updated successfully, but these errors were encountered: