Update ts-node: 10.2.1 → 10.4.0 (minor)

[depfu]

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ ts-node (10.2.1 → 10.4.0) · Repo

Release Notes

10.4.0

Added

• Adds support for targets "es2020" and "es2021" to swc transpiler (#1521)
• Adds automatic target downgrade when using older versions of swc (#1521)
  • If tsconfig specifies es2020, but your version of swc only supports up to es2019, ts-node will automatically switch to es2019 instead of throwing an error

Changed

• Improves types and API docs for creatEsmHooks (API docs) (#1506, #1529)

Fixed

• Fix #1526: data URL handling in new ESM loader hooks API (#1526, #1529)

v10.3.1...v10.4.0
https://github.com/TypeStrong/ts-node/milestone/8

10.3.1

Fixed

• Add version check to use new loader hooks API for node >=16.12.0 (#1522) @shrujalshah28

v10.3.0...v10.3.1
https://github.com/TypeStrong/ts-node/milestone/7

10.3.0

Questions about this release? Ask in the official discussion thread: #1507

Added

• Declare types for node builtin modules within REPL so you do not need to import them (#1424, #1500)
  • Node REPL exposes builtin modules as globals; typechecker now understands this
  • Typechecking should no longer raise errors when using builtins without first importing
  • For example: util.promisify(setTimeout)(1000) or fs.readFileSync('example.txt')
• Add createEsmHooks() function to create ESM loader hooks (API docs) (#1439) @nonara
  • Can be used to compose our loader hooks with another loader or additional logic
• register() accepts a ts-node Service (API docs) (#1474)
  • register(options) is still supported; no breaking changes
• Add support for Node.js's new loader hooks API (#1372, #1457, #1007) @jonaskello
  • Node.js has changed their loader hooks API
  • ts-node is compatible with all node versions, detects your node version and exposes the correct hooks API
  • Node's new API currently only available in node v17 nightly builds
  • Node will eventually backport the changes to node 16, and may also be backport to 14 and 12
• Add --emit to --help output (#1400, #1484) @markbradley27

Changed

• When ts-node is registered and other libraries require('source-map-support'), they will be redirected to @cspotcode/source-map-support
  • See complete description in Fixed section below

Fixed

• Fix #1440, #1441, #1438, #1495: Incorrect stack traces when third-party libraries use source-map-support instead of @cspotcode/source-map-support (#1440, #1441, #1438, #1495, cspotcode/node-source-map-support#23, #1496, #1497) @ejose19
  • When ts-node is registered and other libraries require('source-map-support'), they will be redirected to @cspotcode/source-map-support
  • ts-node uses @cspotcode/source-map-support for the fixes and enhancements listed here: @cspotcode/source-map-support changelog
  • To ensure correct stack traces, all libraries must share a compatible sourcemap support implementation
• Fix #1363: REPL may erroneously combine previous input with next input, eval both as a single statement (#1363, #1480) @TheUnlocked
  • For example, entering 100 on first line and * 2 on second line would erronously be interpreted as 100 * 2
  • REPL now ensures both lines are separate statements, both when typechecking and when evaluating
• Fix #1488: Node may log "circular dependency" warning when using allowJs (#1488, #1489)
• Fix #1301: Filter empty strings from TS_NODE_IGNORE and TS_NODE_IGNORE_DIAGNOSTICS; treat empty environment variable as empty array (#1301, #1483) @ValeriaVG
  • TS_NODE_IGNORE= ts-node ./example.ts will disable default ignore rules; will compile files in ./node_modules

Docs

• Update VSCode debug configuration (Docs) (#1466)
• Update ESM-related messaging to clarify that experimental status is due to Node.js, not ts-node (#1455)
• Refer to ts-node consistently (#1481) @animafps

v10.2.1...v10.3.0
https://github.com/TypeStrong/ts-node/milestone/5

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 28 commits:

• 10.4.0
• update api-extractor report
• Rebuild readme
• Docs merge for 10.3.2 (#1530)
• Fix data URL format determination in new loader hooks API (#1529)
• add Target ES2021 mapping in transpilers/swc (#1521)
• 10.3.1
• update version checks for v16 (#1522)
• Add info about tests to CONTRIBUTING.md (#1520)
• 10.3.0
• add template for release notes
• update api-extractor report for 10.3.0
• update the readme
• Docs -> main for 10.3.0 release (#1502)
• Amending #1496: Redirect source-map-support to @cspotcode/source-map-support (#1497)
• Declare types for node builtin modules in REPL so you do not need to import them (#1500)
• Update esm loader hooks API (#1457)
• Feature: Expose esm hooks factory to public API (#1439)
• Allow composing `register(create())`; refactor tests (#1474)
• Redirect source-map-support to @cspotcode/source-map-support (#1496)
• Fix #1488: circular dependency issue in dist-raw (#1489)
• Fix flaky tests (#1486)
• Fix REPL bug with previous line carryover (#1480)
• fix: Filter empty strings out of list options (#1483)
• Adds --emit to --help output. (#1484)
• Refactor tests and bump TS version (#1475)
• Create SECURITY.md (#1469)
• Update bug-report.md

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)