remove cwd
option, or at least stop resolving entrypoint relative to it
#1834
Milestone
cwd
option, or at least stop resolving entrypoint relative to it
#1834
Today,
cwd
affects resolution of the entrypoint so when youts-node --cwd foo bar.ts
then you runfoo/bar.ts
Seems nice enough from a user perspective, but from a maintenance and compatibility perspective it gets hairy. Cuz what should happen when user code forks a child process in a different working directory, expecting the entrypoint for that child process to be resolved relative to that working directory.
#1814 (comment)
It's not clear we should even have a
--cwd
option.tsc
andnode
do not. At the very least, it shouldn't be affecting the resolution of entrypoint scripts. That makes us incompatible withnode
and it's feature creep.The text was updated successfully, but these errors were encountered: