TypeStrong/ts-node
### [`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
Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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 contains the following updates:
10.1.0->10.2.0Release Notes
TypeStrong/ts-node
### [`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/2Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.
This PR has been generated by WhiteSource Renovate. View repository job log here.