Update dependency ts-node to v10 #26

renovate · 2021-10-22T17:00:48Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
ts-node (source)	`8.10.2` -> `10.4.0`

Release Notes

TypeStrong/ts-node

`v10.4.0`

Compare Source

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)

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

`v10.3.1`

Compare Source

Fixed

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

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

`v10.3.0`

Compare Source

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

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

`v10.2.1`

Compare Source

Fixed

Fixes #1426: Do not import typescript outside of configuration/project loading (#1433, #1426) @Songkeys
- We take care to load your project's version of typescript, falling back to a globally-installed version if necessary.
- 10.2.0 introduced a bug where we did not do this consistently, causing global or npx installations of ts-node to attempt loading typescript relative to themselves, not your project.
- This failed if typescript was not globally installed or npx did not install peer dependencies.

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

`v10.2.0`

Compare Source

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

Added

Adds top-level await support to REPL (#1383, #245) @ejose19
- can be disabled with --no-experimental-repl-await, experimentalReplAwait, or TS_NODE_EXPERIMENTAL_REPL_AWAIT (CLI docs, API docs)
Setting "pretty": false disables pretty formatting of diagnostics even when stdout is a TTY (#1418, #1420) @elevatebart
- Applies to ts-node's pretty option, not to be confused with TypeScript's pretty option
Ignores diagnostics which are annoying in an interactive REPL (#1396, #1120, #729, #850, #469)
- For example, when you input const foo = 1 in the REPL, foo is unused. We ignore the resulting diagnostic foo is declared but its value is never read
- Diagnostics are only ignored in the REPL
- Diagnostics for non-REPL files imported by the REPL will still be shown
Logged stack traces are colorized to match vanilla node's behavior (#1412, #1405)

Fixed

Fix #1397: SWC transpiler should emit ECMAScript imports and exports when configuration dictates (#1409, #1397)
- Enables SWC transpiler to be used alongside --loader
Fix #1403: source-map-support breaks rendering of node errors (#1405, #1403)
Fix #1410: rendering of async stack frames should include async annotations (#1405, #1410)
Fix #1411: wrong order of process 'exit' event and logging unhandled exception (#1405, #1411)
Fix #1419: Should not throw require.resolve error when @types/node peerDependency is missing (#1419, #1422)

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

`v10.1.0`

Compare Source

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

Added

Add "moduleType" option to override module type -- CommonJS or ECMAScript -- on select files. (docs) (#1342, #1371, #1376)
- Useful when a configuration file, for example webpack.config.ts, must execute as CommonJS but the rest of the project is ESM
- selectively overrides package.json "type" and tsconfig.json "module"
- akin to .cjs and .mjs extensions, but for .ts and .tsx files
- thanks to @jayaddison for help on test coverage
Implement "extends" support for "ts-node" options in tsconfig.json (#1328, #1356)
- "ts-node": {} options will be parsed from extended tsconfigs
- allows sharing and deduplicating ts-node configuration
Un-deprecate scope and scopeDir; add both to CLI and tsconfig.json options; un-deprecate TS_NODE_SCOPE env var; add TS_NODE_SCOPE_DIR env var (docs) (#1346, #1367)

Changed

Improve error messages thrown by native ESM loader hooks (#1357, #1373) @tars0x9752
- messages more closely match node; are more descriptive
Emit "ts-node" object at the top of --showConfig output instead of the bottom (#1355)

Fixed

Fix #1282: Set correct globals in [stdin], [eval], and <repl> contexts (#1333)
- More closely align ts-node's behavior with vanilla node
- Affects the interactive REPL, piping to stdin, and ts-node -e
- Matches node's behavior for globals __filename, __dirname, module and sub-fields of module, exports, and builtin module aliases fs, etc
Fix #1343: Set swc option keepClassNames to true (#1344)
Fix: #1387: REPL outputs 'use strict' after first empty line of input (#1388) @ejose19

Docs

Update ESM docs to say that env vars are supported with node --loader ts-node/esm (docs) (#1379)

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

`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)

`v9.0.0`

Compare Source

Breaking changes are labelled [BREAKING] below.

Added

Throw ERR_REQUIRE_ESM when a file is require()d which should be loaded as ESM (#1031)
Re-add "exports" declaration to package.json in backwards-compatible way, enabling node --loader ts-node/esm without file extension (#1028)
Allow specifying "require" option via tsconfig (#925)
REPL respects node's NODE_NO_READLINE environment variable (#1090)
Add a transpile-only entrypoint for ESM loader: node --loader ts-node/esm/transpile-only (#1102) @concision

Changed

[BREAKING] Drops support for node versions < 10 (#1036)

Fixed

[BREAKING] Re-add realpath, which should fix workflows that use symlinks, such as pnpm, Lerna workspaces, or other mono-repo configurations (#970)
Compile files within node_modules when --skip-ignore or --ignore options are configured to allow it (#970)
Fix #884 by not adding all referenced files to getSourceFileNames/rootNames (#999)
Fix #996: bump projectVersion every time getSourceFileNames changes, avoiding accidentally outdated typechecking (#998)
Fix #1051: pass transformers object to ts.transpileModule (#1054) @thetutlage
Fix #1060: use source maps for stack traces in ESM modules (#1087)
Fix #1072: Respect --experimental-specifier-resolution coming from NODE_OPTIONS in ESM loader (#1085) @evg656e
Fix #1098: ESM loader should skip .cjs, .mjs, and any unexpected file extensions (#1103) @concision

Docs

Better explain how to compile imports, either CommonJS or using experimental ESM loader. Resolves #1075 (#1086)

Misc

Fix, re-enable, and add various tests (#1044, #1088, #1108, #1110, #1109, #1115, #1043, #999)

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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, click this checkbox.

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

renovate · 2021-10-22T17:00:51Z

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm WARN using --force Recommended protections disabled.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: angular9-fundamentals-workshop@0.0.0
npm ERR! Found: typescript@4.5.2
npm ERR! node_modules/typescript
npm ERR!   dev typescript@"4.5.2" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer typescript@">=4.4.2 <4.5" from @angular/compiler-cli@13.0.2
npm ERR! node_modules/@angular/compiler-cli
npm ERR!   dev @angular/compiler-cli@"13.0.2" from the root project
npm ERR!   peer @angular/compiler-cli@"^13.0.0" from @angular-devkit/build-angular@13.0.3
npm ERR!   node_modules/@angular-devkit/build-angular
npm ERR!     dev @angular-devkit/build-angular@"13.0.3" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate-cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate-cache/others/npm/_logs/2022-01-09T18_48_36_463Z-debug-0.log

renovate bot force-pushed the renovate/ts-node-10.x branch from 421dd84 to 317befb Compare October 22, 2021 20:52

Update dependency ts-node to v10

f94e6e7

renovate bot force-pushed the renovate/ts-node-10.x branch from 317befb to f94e6e7 Compare January 9, 2022 18:48

howdyAnkit merged commit c0d9f04 into 00-start Jan 24, 2022

renovate bot deleted the renovate/ts-node-10.x branch January 24, 2022 18:19

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update dependency ts-node to v10 #26

Update dependency ts-node to v10 #26

renovate bot commented Oct 22, 2021 •

edited

Loading

renovate bot commented Oct 22, 2021 •

edited

Loading

Update dependency ts-node to v10 #26

Update dependency ts-node to v10 #26

Conversation

renovate bot commented Oct 22, 2021 • edited Loading

Release Notes

Configuration

renovate bot commented Oct 22, 2021 • edited Loading

⚠ Artifact update problem

File name: package-lock.json

renovate bot commented Oct 22, 2021 •

edited

Loading

renovate bot commented Oct 22, 2021 •

edited

Loading