search

SmartBear / git-en-boite

Web service facade for interacting with git repos on various providers - GitHub/BitBucket/GitLab etc.
MIT License
18 stars 7 forks source link

Update dependency ts-node to v10.4.0 #824

Closed mend-for-github-com[bot] closed 2 years ago

mend-for-github-com[bot] commented 2 years ago

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
ts-node (source) 10.0.0 -> 10.4.0 age adoption passing confidence

Release Notes

TypeStrong/ts-node ### [`v10.4.0`](https://togithub.com/TypeStrong/ts-node/releases/v10.4.0) [Compare Source](https://togithub.com/TypeStrong/ts-node/compare/v10.3.1...v10.4.0) **Added** - Adds support for targets "es2020" and "es2021" to swc transpiler ([#​1521](https://togithub.com/TypeStrong/ts-node/issues/1521)) - Adds automatic target downgrade when using older versions of swc ([#​1521](https://togithub.com/TypeStrong/ts-node/issues/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](https://typestrong.org/ts-node/api/index.html#createEsmHooks)) ([#​1506](https://togithub.com/TypeStrong/ts-node/issues/1506), [#​1529](https://togithub.com/TypeStrong/ts-node/issues/1529)) **Fixed** - Fix [#​1526](https://togithub.com/TypeStrong/ts-node/issues/1526): data URL handling in new ESM loader hooks API ([#​1526](https://togithub.com/TypeStrong/ts-node/issues/1526), [#​1529](https://togithub.com/TypeStrong/ts-node/issues/1529)) https://github.com/TypeStrong/ts-node/milestone/8 ### [`v10.3.1`](https://togithub.com/TypeStrong/ts-node/releases/v10.3.1) [Compare Source](https://togithub.com/TypeStrong/ts-node/compare/v10.3.0...v10.3.1) **Fixed** - Add version check to use new loader hooks API for node >=16.12.0 ([#​1522](https://togithub.com/TypeStrong/ts-node/issues/1522)) [@​shrujalshah28](https://togithub.com/shrujalshah28) https://github.com/TypeStrong/ts-node/milestone/7 ### [`v10.3.0`](https://togithub.com/TypeStrong/ts-node/releases/v10.3.0) [Compare Source](https://togithub.com/TypeStrong/ts-node/compare/v10.2.1...v10.3.0) Questions about this release? Ask in the official discussion thread: [#​1507](https://togithub.com/TypeStrong/ts-node/issues/1507) **Added** - Declare types for node builtin modules within REPL so you do not need to import them ([#​1424](https://togithub.com/TypeStrong/ts-node/issues/1424), [#​1500](https://togithub.com/TypeStrong/ts-node/issues/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](https://typestrong.org/ts-node/api/index.html#createEsmHooks)) ([#​1439](https://togithub.com/TypeStrong/ts-node/issues/1439)) [@​nonara](https://togithub.com/nonara) - Can be used to compose our loader hooks with another loader or additional logic - `register()` accepts a ts-node `Service` ([API docs](https://typestrong.org/ts-node/api/index.html#register)) ([#​1474](https://togithub.com/TypeStrong/ts-node/issues/1474)) - `register(options)` is still supported; no breaking changes - Add support for Node.js's new loader hooks API ([#​1372](https://togithub.com/TypeStrong/ts-node/issues/1372), [#​1457](https://togithub.com/TypeStrong/ts-node/issues/1457), [#​1007](https://togithub.com/TypeStrong/ts-node/issues/1007)) [@​jonaskello](https://togithub.com/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](https://togithub.com/TypeStrong/ts-node/issues/1400), [#​1484](https://togithub.com/TypeStrong/ts-node/issues/1484)) [@​markbradley27](https://togithub.com/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](https://togithub.com/TypeStrong/ts-node/issues/1440), [#​1441](https://togithub.com/TypeStrong/ts-node/issues/1441), [#​1438](https://togithub.com/TypeStrong/ts-node/issues/1438), [#​1495](https://togithub.com/TypeStrong/ts-node/issues/1495): Incorrect stack traces when third-party libraries use `source-map-support` instead of `@cspotcode/source-map-support` ([#​1440](https://togithub.com/TypeStrong/ts-node/issues/1440), [#​1441](https://togithub.com/TypeStrong/ts-node/issues/1441), [#​1438](https://togithub.com/TypeStrong/ts-node/issues/1438), [#​1495](https://togithub.com/TypeStrong/ts-node/issues/1495), [cspotcode/node-source-map-support#​23](https://togithub.com/cspotcode/node-source-map-support/issues/23), [#​1496](https://togithub.com/TypeStrong/ts-node/issues/1496), [#​1497](https://togithub.com/TypeStrong/ts-node/issues/1497)) [@​ejose19](https://togithub.com/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](https://togithub.com/cspotcode/node-source-map-support/issues/24) - To ensure correct stack traces, all libraries must share a compatible sourcemap support implementation - Fix [#​1363](https://togithub.com/TypeStrong/ts-node/issues/1363): REPL may erroneously combine previous input with next input, eval both as a single statement ([#​1363](https://togithub.com/TypeStrong/ts-node/issues/1363), [#​1480](https://togithub.com/TypeStrong/ts-node/issues/1480)) [@​TheUnlocked](https://togithub.com/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](https://togithub.com/TypeStrong/ts-node/issues/1488): Node may log "circular dependency" warning when using `allowJs` ([#​1488](https://togithub.com/TypeStrong/ts-node/issues/1488), [#​1489](https://togithub.com/TypeStrong/ts-node/issues/1489)) - Fix [#​1301](https://togithub.com/TypeStrong/ts-node/issues/1301): Filter empty strings from `TS_NODE_IGNORE` and `TS_NODE_IGNORE_DIAGNOSTICS`; treat empty environment variable as empty array ([#​1301](https://togithub.com/TypeStrong/ts-node/issues/1301), [#​1483](https://togithub.com/TypeStrong/ts-node/issues/1483)) [@​ValeriaVG](https://togithub.com/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](https://typestrong.org/ts-node/docs/recipes/visual-studio-code)) ([#​1466](https://togithub.com/TypeStrong/ts-node/issues/1466)) - Update ESM-related messaging to clarify that experimental status is due to Node.js, not ts-node ([#​1455](https://togithub.com/TypeStrong/ts-node/issues/1455)) - Refer to ts-node consistently ([#​1481](https://togithub.com/TypeStrong/ts-node/issues/1481)) [@​animafps](https://togithub.com/animafps) https://github.com/TypeStrong/ts-node/milestone/5 ### [`v10.2.1`](https://togithub.com/TypeStrong/ts-node/releases/v10.2.1) [Compare Source](https://togithub.com/TypeStrong/ts-node/compare/v10.2.0...v10.2.1) **Fixed** - Fixes [#​1426](https://togithub.com/TypeStrong/ts-node/issues/1426): Do not import typescript outside of configuration/project loading ([#​1433](https://togithub.com/TypeStrong/ts-node/issues/1433), [#​1426](https://togithub.com/TypeStrong/ts-node/issues/1426)) [@​Songkeys](https://togithub.com/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`](https://togithub.com/TypeStrong/ts-node/releases/v10.2.0) [Compare Source](https://togithub.com/TypeStrong/ts-node/compare/v10.1.0...v10.2.0) Questions about this release? Ask in the official discussion thread: [#​1423](https://togithub.com/TypeStrong/ts-node/issues/1423) **Added** - Adds top-level await support to REPL ([#​1383](https://togithub.com/TypeStrong/ts-node/issues/1383), [#​245](https://togithub.com/TypeStrong/ts-node/issues/245)) [@​ejose19](https://togithub.com/ejose19) - can be disabled with `--no-experimental-repl-await`, `experimentalReplAwait`, or `TS_NODE_EXPERIMENTAL_REPL_AWAIT` ([CLI docs](https://typestrong.org/ts-node/docs/options), [API docs](https://typestrong.org/ts-node/api/interfaces/CreateOptions.html#experimentalReplAwait)) - Setting `"pretty": false` disables pretty formatting of diagnostics even when stdout is a TTY ([#​1418](https://togithub.com/TypeStrong/ts-node/issues/1418), [#​1420](https://togithub.com/TypeStrong/ts-node/issues/1420)) [@​elevatebart](https://togithub.com/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](https://togithub.com/TypeStrong/ts-node/issues/1396), [#​1120](https://togithub.com/TypeStrong/ts-node/issues/1120), [#​729](https://togithub.com/TypeStrong/ts-node/issues/729), [#​850](https://togithub.com/TypeStrong/ts-node/issues/850), [#​469](https://togithub.com/TypeStrong/ts-node/issues/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](https://togithub.com/TypeStrong/ts-node/issues/1412), [#​1405](https://togithub.com/TypeStrong/ts-node/issues/1405)) **Fixed** - Fix [#​1397](https://togithub.com/TypeStrong/ts-node/issues/1397): SWC transpiler should emit ECMAScript imports and exports when configuration dictates ([#​1409](https://togithub.com/TypeStrong/ts-node/issues/1409), [#​1397](https://togithub.com/TypeStrong/ts-node/issues/1397)) - Enables SWC transpiler to be used alongside `--loader` - Fix [#​1403](https://togithub.com/TypeStrong/ts-node/issues/1403): source-map-support breaks rendering of node errors ([#​1405](https://togithub.com/TypeStrong/ts-node/issues/1405), [#​1403](https://togithub.com/TypeStrong/ts-node/issues/1403)) - Fix [#​1410](https://togithub.com/TypeStrong/ts-node/issues/1410): rendering of async stack frames should include `async` annotations ([#​1405](https://togithub.com/TypeStrong/ts-node/issues/1405), [#​1410](https://togithub.com/TypeStrong/ts-node/issues/1410)) - Fix [#​1411](https://togithub.com/TypeStrong/ts-node/issues/1411): wrong order of process 'exit' event and logging unhandled exception ([#​1405](https://togithub.com/TypeStrong/ts-node/issues/1405), [#​1411](https://togithub.com/TypeStrong/ts-node/issues/1411)) - Fix [#​1419](https://togithub.com/TypeStrong/ts-node/issues/1419): Should not throw `require.resolve` error when `@types/node` peerDependency is missing ([#​1419](https://togithub.com/TypeStrong/ts-node/issues/1419), [#​1422](https://togithub.com/TypeStrong/ts-node/issues/1422)) https://github.com/TypeStrong/ts-node/milestone/2 ### [`v10.1.0`](https://togithub.com/TypeStrong/ts-node/releases/v10.1.0) [Compare Source](https://togithub.com/TypeStrong/ts-node/compare/v10.0.0...v10.1.0) Questions about this release? Ask in the official discussion thread: [#​1390](https://togithub.com/TypeStrong/ts-node/issues/1390) **Added** - Add `"moduleType"` option to override module type -- CommonJS or ECMAScript -- on select files. ([docs](https://typestrong.org/ts-node/docs/module-type-overrides)) ([#​1342](https://togithub.com/TypeStrong/ts-node/issues/1342), [#​1371](https://togithub.com/TypeStrong/ts-node/issues/1371), [#​1376](https://togithub.com/TypeStrong/ts-node/issues/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](https://togithub.com/jayaddison) for help on test coverage - Implement `"extends"` support for `"ts-node"` options in `tsconfig.json` ([#​1328](https://togithub.com/TypeStrong/ts-node/issues/1328), [#​1356](https://togithub.com/TypeStrong/ts-node/issues/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](https://typestrong.org/ts-node/docs/options)) ([#​1346](https://togithub.com/TypeStrong/ts-node/issues/1346), [#​1367](https://togithub.com/TypeStrong/ts-node/issues/1367)) **Changed** - Improve error messages thrown by native ESM loader hooks ([#​1357](https://togithub.com/TypeStrong/ts-node/issues/1357), [#​1373](https://togithub.com/TypeStrong/ts-node/issues/1373)) [@​tars0x9752](https://togithub.com/tars0x9752) - messages more closely match node; are more descriptive - Emit `"ts-node"` object at the top of `--showConfig` output instead of the bottom ([#​1355](https://togithub.com/TypeStrong/ts-node/issues/1355)) **Fixed** - Fix [#​1282](https://togithub.com/TypeStrong/ts-node/issues/1282): Set correct globals in `[stdin]`, `[eval]`, and `` contexts ([#​1333](https://togithub.com/TypeStrong/ts-node/issues/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](https://togithub.com/TypeStrong/ts-node/issues/1343): Set swc option `keepClassNames` to `true` ([#​1344](https://togithub.com/TypeStrong/ts-node/issues/1344)) - Fix: [#​1387](https://togithub.com/TypeStrong/ts-node/issues/1387): REPL outputs 'use strict' after first empty line of input ([#​1388](https://togithub.com/TypeStrong/ts-node/issues/1388)) [@​ejose19](https://togithub.com/ejose19) **Docs** - Update ESM docs to say that env vars *are* supported with `node --loader ts-node/esm` ([docs](https://togithub.com/TypeStrong/ts-node/issues/1007)) ([#​1379](https://togithub.com/TypeStrong/ts-node/issues/1379)) https://github.com/TypeStrong/ts-node/milestone/3

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 these updates again.