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
Ask ts-node not to run anything, but to emit everything matched by --files as compiled output.
Is this request related to a problem?
A way to efficiently pre-compile a project that's been setup to run in ts-node, perhaps using a custom compiler like ttypescript or ts-node/compilers/swc, perhaps using transformers.
Alternatives you've considered
ttypescript / ttsc for transformers
Using swc or esbuild CLI directly
Additional context
This idea's been kicking around my brain for a while, and I want to write it down. Feels like feature-creep, even though I like the idea.
Seems like something people might want. They set up "paths" mappings, set up transformers, test that it works with ts-node, and then they want to compile straight from there without configuring a separate build. Sometimes people reach for ts-node first and then want an easy way to compile after the fact.
I dunno, this idea seems flawed, but maybe I'll figure out how to clean it up enough to be feasible.
The text was updated successfully, but these errors were encountered:
Desired Behavior
Ask
ts-node
not to run anything, but to emit everything matched by--files
as compiled output.Is this request related to a problem?
A way to efficiently pre-compile a project that's been setup to run in
ts-node
, perhaps using a custom compiler likettypescript
orts-node/compilers/swc
, perhaps using transformers.Alternatives you've considered
ttypescript
/ttsc
for transformersUsing
swc
oresbuild
CLI directlyAdditional context
This idea's been kicking around my brain for a while, and I want to write it down. Feels like feature-creep, even though I like the idea.
Seems like something people might want. They set up "paths" mappings, set up transformers, test that it works with
ts-node
, and then they want to compile straight from there without configuring a separate build. Sometimes people reach forts-node
first and then want an easy way to compile after the fact.I dunno, this idea seems flawed, but maybe I'll figure out how to clean it up enough to be feasible.
The text was updated successfully, but these errors were encountered: