Issues: TypeStrong/ts-node
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Inconsistent behaviour with
moduleResolution: "node16" and swc: true for CommonJS module output
#2035
opened Jul 14, 2023 by
jdb8
ERR_MODULE_NOT_FOUND CustomError: Cannot find package when using paths
#2031
opened Jun 21, 2023 by
Jazcash
Node 20: errors produced by
reportTSError are not serialised correctly when using ESM loader
#2026
opened May 23, 2023 by
danrr
ts-node should take into account tsconfig paths in esm mode and keep but transpile imports
#2023
opened May 17, 2023 by
a-x-
It would be better if --esm is automatically specified if the file extension is
.mts
#2022
opened May 16, 2023 by
gfx
ts-node/esm shortcircuits and does not allow downstream loaders to transform the result
#2008
opened May 5, 2023 by
giltayar
Incorrect sourcemapping in files with newlines in Node 20.1
#2006
opened May 4, 2023 by
richardsimko
SWC >= 1.3.50 seems to have introduced breaking issues with ts-node
#1996
opened Apr 19, 2023 by
erikthiem-immuta
Endlessly spawning loaders in node 20.0.0 leading to large memory leak
#1995
opened Apr 19, 2023 by
Jamesernator
Wrong base path determination when ts-node/esm loader is used
#1989
opened Apr 11, 2023 by
ThePlenkov
Require typescript file after ts-node.register doesn't work in ESM
#1986
opened Apr 5, 2023 by
Fernando9995
Export logic for converting
tsconfig into swcrc (or publish it as a separate NPM package)
#1983
opened Mar 31, 2023 by
GreenTea124
Support exports and imports subpath (package.json) pointing to generated .js files
#1974
opened Mar 20, 2023 by
InExtremaRes
Previous Next
ProTip!
Type g i on any issue or pull request to go back to the issue listing page.