ts-node

Fixed

• Fixed tsconfig.json file not found on latest TypeScript version (https://github.com/TypeStrong/ts-node/pull/2091)

Fixed

• Workaround nodejs bug introduced in 18.6.0 (#1838) @cspotcode
  • Only affects projects on node >=18.6.0 using --esm
  • Older versions of node and projects without --esm are unaffected

https://github.com/TypeStrong/ts-node/compare/v10.9.0...v10.9.1 https://github.com/TypeStrong/ts-node/milestone/18?closed=1

Added

• --project accepts path to a directory containing a tsconfig.json (#1829, #1830) @cspotcode
  • previously it required an explicit filename
• Added helpful error message when swc version is too old to support our configuration (#1802) @cspotcode
• Added experimentalTsImportSpecifiers option which allows using voluntary .ts file extensions in import specifiers (undocumented...

Fixed

• Revert "Use file URL for source map paths" (#1821) @cspotcode
  • Fixes #1790: ts-node 10.8.1 regression where nyc code coverage reports had incorrect paths
  • Fixes #1797: ts-node 10.8.1 regression where breakpoints did not hit in VSCode debugging
• Allow JSON imports in node 16.15 and up (#1792) @queengooborg
  • JSON imports were already supported in v17.5 and up
  • this...

Fixed

• Fixed #1769: source URLs in source map cache were malformed on Windows, affecting code coverage reports (#1769, #1771) @PaperStrike
• Fixed #1778: typechecker was erronously resolving imports from ESM files as if they were from CJS files (#1778, #1782) @cspotcode

https://github.com/TypeStrong/ts-node/compare/v10.8.0...v10.8.1 https://github.com/TypeStrong/ts-node/milestone/14