Update dependency ts-node to v10

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
ts-node (source)	^9.0.0 -> ^10.0.0

---

Release Notes

TypeStrong/ts-node

v10.0.0

Compare Source

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

Breaking changes are prefixed with [BREAKING]

Added

• Adds --show-config to log the resolved configuration (docs) (#​1100, #​1243)
• Bundle and re-export @​tsconfig/node* configurations for convenience (docs) (#​1202, #​1236, #​1313)
• Default to appropriate @​tsconfig/node* configuration based on node and typescript versions (docs) (#​1202, #​1236, #​1313)
• Automatically reference @​types/node; use globally-installed @​types/node if not locally installed (#​1240, #​1257)
• Add swc integration and new --transpiler option to use third-party transpilers for a massive speed boost on large codebases (docs) (#​779, #​1160)
• Add scopeDir API option (docs) (#​1155)
• Add projectSearchDir API option (docs) (#​1155)
• Add --cwd-mode and ts-node-cwd to resolve config file relative to cwd, not entrypoint script (#​1155)

Changed

• [BREAKING] Make --script-mode default behavior; resolve tsconfig relative to entrypoint script instead of cwd (#​949, #​1197, #​1155)
  • In most cases this change will have no noticeable effect
  • Primarily benefits portable shell scripts on your $PATH, because ts-node will respect the script's local tsconfig.json
  • Use --cwd-mode or ts-node-cwd if you need legacy behavior
• [BREAKING] ignore rules evaluate relative to tsconfig.json directory, otherwise cwd (#​1155)
• [BREAKING] Remove support for node 10. Minimum supported version is node 12 (#​1312)
• Rename --dir to --cwd; rename TS_NODE_DIR to TS_NODE_CWD (#​1155)
  • --dir and TS_NODE_DIR are deprecated but still parsed for backwards-compatibility
  • --dir effectively changed the working directory of ts-node; renaming makes this behavior more obvious

Deprecated

• Deprecate TS_NODE_SCOPE (#​1155)
• Deprecate --dir and TS_NODE_DIR (#​1155)

Removed

• [BREAKING] Internal APIs removed from type declarations (#​1242)
  • Removed DEFAULTS, normalizeSlashes, parse, split
  • No features were removed
  • This will only affect consumers of ts-node's programmatic API

Fixed

• [BREAKING] Fix #​1229 and #​1235: always throw ERR_REQUIRE_ESM when attempting to execute ESM as CJS, even when not using --loader ts-node/esm (#​1232)
  • This aligns our behavior with vanilla node
• [BREAKING] Fix #​1225: compiler is loaded relative to tsconfig.json instead of entrypoint script (#​1155)
  • In most cases this change will have no noticable effect
• Fix #​1217: REPL not always using passed stdout and stderr (#​1224)
• Fix #​1220: ts-node ./index may execute the wrong file extension because tsconfig search poisons the require.resolve cache (#​1155)
• Fix #​1322: Sourcemaps fail for filenames with spaces or other characters which are percent-encoded in URLs (#​1160, #​1330)
• Fix #​1331: Resolution of node builtin modules in ESM loader fails on node >=12.20.0, <13 (#​1332)

Docs

• New documentation website: https://typestrong.org/ts-node
  • README is generated to match the website
  • Added page explaining CommonJS vs ESM
  • Added page with Performance advice
  • Added Troubleshooting page
  • Organized and added to "Recipes" section with third-party tool integrations
  • Added TypeDoc-generated API docs
  • Work was spread across multiple tickets: #​1207, #​1213, #​1221, #​1228, #​1244, #​1250, #​1294, #​1295, #​1296, #​1297
  • Thanks to these contributors for PRs which improved our documentation
    • add troubleshooting tip for syntax errors (#​1201) @​jedwards1211
    • Clarify handling of tsx/jsx file extensions (#​1179) @​NaridaL
• Added CONTRIBUTING.md to document the codebase and our development workflow

https://github.com/TypeStrong/ts-node/milestone/1

v9.1.1

Compare Source

No code changes. We re-packed and republished v9.1.1, because the v9.1.0 package was broken due to an npm v7 bug.

Fixes

• Published tarball had extra slashes in the paths of dist files. #​1172

v9.1.0

Compare Source

Added

• Expose ts-node REPL via the API (#​1121) @​MarcManiez
• Allow --typeCheck flag to override --transpileOnly flag specified in tsconfig.json (#​1142)

Changed

• Rename interface Register to Service. It is still aliased as Register for backwards compatibility (#​1158)
• Update code copied from node's ESM resolver to be the latest from node 15, to keep our ESM resolver's behavior as close as possible to vanilla node (#​1167)

Fixed

• ESM resolver will preserve search portion of URL, used for cache busting (#​1165) @​frandiox
• Fix ESM resolution of builtin modules on node >=14.13.1 (#​1136)
• Recognize --es-module-specifier-resolution as an alias of --experimental-specifier-resolution for node 12 compatibility (#​1122) @​nguyensomniac

Docs

• Fix description of ts-node-dev in README (#​1131) @​iamandrewluca
• Update transformers description to clarify incompatibility with transpileOnly (#​1123)

Misc

• Changes to test matrix: Test against node 15; drop node 13 tests; remove 12.16 in favor of latest 12.x.x (#​1138, #​1148)
• Improve codecov rules to remove misleading test failures (#​1159)

---

Configuration

📅 Schedule: "before 7am every weekday" in timezone Europe/Brussels.

🚦 Automerge: Disabled due to failing status checks.

♻️ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box.

---

This PR has been generated by WhiteSource Renovate. View repository job log here.

[coveralls]

Pull Request Test Coverage Report for Build 440

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 82.301%

---

Totals
Change from base Build 438:	0.0%
Covered Lines:	1099
Relevant Lines:	1298

---

💛 - Coveralls

[wschella]

This would require us to bump required node version in Comunica to >= 12.0.0. We can reopen if that happens.

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 10.x releases. But if you manually upgrade to 10.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.