chore(deps): update all (major)

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence	Type	Update
@​types/joi	14.3.4 -> 17.2.2					devDependencies	major
@types/node (source)	12.12.44 -> 18.15.10					devDependencies	major
@types/node (source)	10.17.24 -> 18.15.10					devDependencies	major
@​types/pino	6.0.1 -> 7.0.4					devDependencies	major
@types/ws (source)	7.2.5 -> 8.5.4					dependencies	major
docker	17.12.1-ce-git -> 18.06.3-ce-git					docker	major
standard (source)	14.3.4 -> 17.0.0					devDependencies	major
ts-node (source)	8.10.2 -> 10.9.1					devDependencies	major
typescript (source)	3.9.5 -> 5.0.2					devDependencies	major

---

Release Notes

standard/standard

v17.0.0

Compare Source

We're super excited to announce standard 17!

This major release fully focuses on getting in sync with the wider ESLint ecosystem
and doesn't in itself introduce any new rules or features.

When you upgrade, consider running standard --fix to automatically format your
code to match the current set of rules.

This is the first release by two of our standard co-maintainers @​Divlo and @​voxpelli. Buy them a cake if you run into them, thanks for getting this release out!

Major changes

• eslint-config-node has been replaced with the up to date fork eslint-config-n. If you have used comments like // eslint-disable-line node/no-deprecated-api you now have to reference the n/ rules instead.
• object-shorthand rule (as warning)
• Use of ESLint 8, which allows for support for all of the latest syntax that ESLint 8 includes, such as top level await #​1548 #​1775
• --verbose by default

Changed features

• Update eslint from ~7.18.0 to ^8.13.0
• Update eslint-config-standard from 16.0.3 to 17.0.0 to adapt to ESLint 8
• Update eslint-config-standard-jsx from 10.0.0 to ^11.0.0 to adapt to ESLint 8
• Update standard-engine from ^14 to ^15.0.0 to adapt to ESLint 8, see its CHANGELOG
• Move from eslint-plugin-node@~11.1.0 to eslint-plugin-n@^15.1.0 to adapt to ESLint 8
• Update eslint-plugin-import from ~2.24.2 to ^2.26.0
• Update eslint-plugin-promise from ~5.1.0 to ^6.0.0
• Update eslint-plugin-react from ~7.25.1 to ^7.28.0

v16.0.4

Compare Source

• Update eslint from ~7.13.1 to ~7.18.0
• Update eslint-config-standard from 16.0.2 to 16.0.3
• Update eslint-plugin-import from ~2.22.1 to ~2.24.2
• Update eslint-plugin-promise from ~4.2.1 to ~5.1.0
• Update eslint-plugin-react from ~7.21.5 to ~7.25.1

v16.0.3

Compare Source

• Update eslint from ~7.12.1 to ~7.13.0
• Relax rule: Enforce default parameters to be last #​1414

v16.0.2

Compare Source

• Allow standard to run on Node 11, even though it's not officially supported #​1597

v16.0.1

Compare Source

• Introduce "warning" system for disruptive rules (read more below)
• Change rule to a "warning": Require let or const instead of var (no-var) #​633

standard treats all rule violations as errors, which means that standard
will exit with a non-zero (error) exit code.

However, we may occasionally release a new major version of standard
which changes a rule that affects the majority of standard users (for example,
transitioning from var to let/const). We do this only when we think the
advantage is worth the cost and only when the rule is
auto-fixable.

In these situations, we have a "transition period" where the rule change is only
a "warning". Warnings don't cause standard to return a non-zero (error)
exit code. However, a warning message will still print to the console. During
the transition period, using standard --fix will update your code so that it's
ready for the next major version.

The slow and careful approach is what we strive for with standard. We're
generally extremely conservative in enforcing the usage of new language
features. We want using standard to be light and fun and so we're careful
about making changes that may get in your way. As always, you can
disable a rule at any time, if necessary.

v16.0.0

Compare Source

We're super excited to announce standard 16!

As with every new major release, there are lots of new rules in 16.0.0 designed
to help catch bugs and make programmer intent more explicit. This release brings
better performance, tons of bug fixes, improved JSX, React ⚛️, and Next.js support!

When you upgrade, consider running standard --fix to automatically format your
code to match the newly added rules.

❤️ If you enjoy StandardJS and want to support future releases, please
support Feross!

New features

• 🏎 Better performance: the filesystem doesn't need to be traversed multiple times! #​1023

  • Massive improvements (on the order of minutes!) for projects with huge folders which are are ignored with .gitignore

• 🌟 Support the .gitignore ignore syntax from the command line #​1117

  • In older versions, the command standard src would not lint the src/ folder
  • Instead, a glob pattern like standard src/**/*.js was required
  • This is now fixed! You can run standard src to lint the src/ folder!

• 🌟 Support relative paths from the command line in more situations (e.g. standard ../src/*.js) #​1384

• 🌟 New extensions option for linting additional extensions besides .js, .jsx, .mjs, and .cjs

  • Can be configured with the --ext command line flag or in package.json:

  • Example:

    standard --ext .ts

    {
      "standard": {
        "extensions": [".ts"]
      }
    }

• 🌟 New cache directory location, respecting XDG_CACHE_HOME preference, with fallback to ~/.cache/standard standard-engine/#​214

Changed features

• Update eslint from ~7.11.0 to ~7.12.1

• Update standard-engine from ^12 to ^14

  • Fix inaccurate --help command which indicates that bundle.js is automatically ignored when it is not anymore standard-engine/#​224
  • Remove deglob package and use built-in ESLint folder-traversal support

• Paths with square brackets (e.g. [ and ]) are no longer skipped #​1333

  • This pattern is particularly common in Next.js apps, e.g. blog/[slug].js
  • You may notice new errors in these files since they were not being linted before

• Better mono-repo support: Nested node_modules/ folders are ignored by default #​1182

• Remove eslint-plugin-standard #​1316

  • We migrated the remaining no-callback-literal rule into eslint-plugin-node

New rules

(Estimated % of affected standard users, based on test suite in parens)

• Require let or const instead of var (no-var) #​633 [75%] [automatic fixing reduces to 11%]
• Enforce return statements in Array method callbacks (array-callback-return) #​859 [7%]
• Disallow empty block statements (no-empty) #​796 [2%]
• Enforce default parameters to be last (default-param-last) #​1414 [1%]
• Disallow use of the RegExp constructor in favor of regular expression literals (prefer-regex-literals) #​1413 [1%]
• Disallow spaces inside of computed keys of class methods, getters and setters (computed-property-spacing) #​1416 [0%]
• Disallow case NaN, switch(NaN), indexOf(NaN), and lastIndexOf(NaN) (use-isnan) #​1429 [0%]
• Disallow assigning to imported bindings (no-import-assign) #​1412 [0%]
• Enforce getter/setter pairs in classes (accessor-pairs) #​1415 [0%]
• Node: Disallow assignment to exports (node/no-exports-assign) #​1400 [0%]
• React: Prevent usage of the return value of ReactDOM.render (react/no-render-return-value) #​1568 [1%]
• React: Prevent usage of deprecated methods (react/no-deprecated) #​1572 [1%]
• React: Prevent direct mutation of this.state (react/no-direct-mutation-state) #​1571 [0%]
• React: Prevent usage of findDOMNode (react/no-find-dom-node) #​1570 [0%]
• React: Prevent usage of isMounted (react/no-is-mounted) #​1569 [0%]
• React: Prevent using string refs (react/no-string-refs) #​1567 [0%]
• JSX: Prevent missing parentheses around multiline JSX (react/jsx-wrap-multilines) #​710 #​1382 (0%)
• JSX: Check if shorthand fragment syntax requires a key prop (react/jsx-key) #​1575 [0%]
• JSX: Prevent passing of children as props (react/no-children-prop) #​1574 [0%]
• JSX: Prevent using children and dangerouslySetInnerHTML as props at the same time (react/no-danger-with-children) #​1573 [0%]
• JSX: Prevent invalid characters from appearing in markup (react/no-unescaped-entities) #​1566 [0%]
• JSX: Enforce JSX value is returned in component render function (react/require-render-return) #​1565 [0%]
• JSX: Prevent usage of unsafe target='_blank' on any component named Link (react/jsx-no-target-blank) #​1576 [0%]

Changed rules

• Relax rule: JSX: Consider the global scope when checking for defined Components #​1115
• Relax rule: JSX: Remove conflicting indentation rule in indent #​1499

v15.0.1

Compare Source

• Relax rule: Remove conflicting JSX indenting with indent rule eslint-config-standard/#​177

v15.0.0

Compare Source

We're super excited to announce standard 15!

As with every new major release, there are lots of new rules in 15.0.0 designed
to help catch bugs and make programmer intent more explicit. This release brings
support for ES 2021, the latest version of the ECMAScript specification, as well
as many quality-of-life improvements, including ESLint v7.

When you upgrade, consider running standard --fix to automatically format your
code to match the newly added rules.

❤️ If you enjoy StandardJS and want to support future releases, check out
Feross's GitHub Sponsors page.

New features

• Support ES 2021, the latest version of the ECMAScript specification, which includes support for logical assignment operators and numeric separators #​1551
• Support ES 2020 features such as optional chaining, the nullish coalescing operator, export * as ns from 'source', and import.meta.
• Support global variables from ES 2017 (Atomics, SharedArrayBuffer), ES 2020 (BigInt, BigInt64Array, BigUint64Array, globalThis), and ES 2021 (FinalizationRegistry, WeakRef). #​1436 #​1557 eslint-config-standard/#​156
• The documentation is now available in Indonesian 🇮🇩! #​1544
  • Thanks to @​yoga1234 for the excellent work!
  • Other community contributed translations exist in Spanish, French, Italian, Japanese, Korean, Portuguese, Simplified Chinese, and Taiwanese Mandarin.
  • More translations are always welcome!

Changed features

• BREAKING: Node.js 8 is no longer supported
  • Node.js 8 is EOL and will no longer be receiving security updates.
  • To prevent breaking CI for projects which still support Node 8, standard silently passes when run by an unsupported version of Node
• Update eslint from ~6.8.0 to ~7.11.0

New rules

(Estimated % of affected standard users, based on test suite in parens)

• Require indentation for values of ternary expressions (indent) #​927 [4%]
• Enforce newlines between operands of ternary expressions if the expression spans multiple lines (multiline-ternary) #​1558 [3%]
• Disallow loops with a body that allows only one iteration (no-unreachable-loop) #​1556 [0%]
• Disallow useless backreferences in regular expressions (no-useless-backreference) #​1554 [0%]
• Enforce default clauses in switch statements to be last (default-case-last) #​1553 [0%]
• Disallow Number Literals That Lose Precision (no-loss-of-precision) #​1552 [0%]

Changed rules

• Relax rule: Allow function declarations in nested blocks #​1406
• Relax rule: Removed redundant no-negated-in-lhs rule, already enforced by no-unsafe-negation eslint-config-standard/#​160

TypeStrong/ts-node

v10.9.1

Compare Source

Fixed

• Workaround nodejs bug introduced in 18.6.0 (#​1838) @​cspotcode
  • Only affects projects on node >=18.6.0 using --esm
  • Older versions of node and projects without --esm are unaffected

https://github.com/TypeStrong/ts-node/milestone/18?closed=1

v10.9.0

Compare Source

Added

• --project accepts path to a directory containing a tsconfig.json (#​1829, #​1830) @​cspotcode
  • previously it required an explicit filename
• Added helpful error message when swc version is too old to support our configuration (#​1802) @​cspotcode
• Added experimentalTsImportSpecifiers option which allows using voluntary .ts file extensions in import specifiers (undocumented except for API docs) (#​1815) @​cspotcode

Fixed

• Fixed bug where child_process.fork() would erroneously execute the parent's entrypoint script, not the intended child script (#​1812, #​1814) @​devversion
• Fixed support for jsx modes "react-jsx" and "react-jsxdev" in swc transpiler (#​1800, #​1802) @​cspotcode
• Fixed support for import assertions in swc transpiler (#​1817, #​1802) @​cspotcode
• Fixed bug where calling repl.evalCode() with code not ending in a newline would not update the typechecker accordingly (#​1764, #​1824) @​cspotcode

https://github.com/TypeStrong/ts-node/milestone/16?closed=1

v10.8.2

Compare Source

Fixed

• Revert "Use file URL for source map paths" (#​1821) @​cspotcode
  • Fixes #​1790: ts-node 10.8.1 regression where nyc code coverage reports had incorrect paths
  • Fixes #​1797: ts-node 10.8.1 regression where breakpoints did not hit in VSCode debugging
• Allow JSON imports in node 16.15 and up (#​1792) @​queengooborg
  • JSON imports were already supported in v17.5 and up
  • this change extends support to >=16.15.0,<17.0.0
  • These version ranges match vanilla node's support for JSON imports

https://github.com/TypeStrong/ts-node/milestone/15?closed=1

v10.8.1

Compare Source

Fixed

• Fixed #​1769: source URLs in source map cache were malformed on Windows, affecting code coverage reports (#​1769, #​1771) @​PaperStrike
• Fixed #​1778: typechecker was erronously resolving imports from ESM files as if they were from CJS files (#​1778, #​1782) @​cspotcode

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

v10.8.0

Compare Source

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

Added

• Added support for module=NodeNext, module=Node16, .mts, .cts, .mjs, and .cjs file extensions (#​1414, #​1694, #​1744, #​1745, #​1727, #​1717, #​1753, #​1757) @​cspotcode
  • For best results, enable experimentalResolver (docs)
  • See TypeScript's official documentation: https://www.typescriptlang.org/docs/handbook/esm-node.html
  • enables mixed-mode projects with both ESM and CommonJS
  • enables all supported file extensions in TypeScript 4.7
  • Obeys package.json "type"
• Added ability to include file extensions in CommonJS imports (#​1727, #​1753) @​cspotcode
  • Enables consistency with ESM, where file extensions are often mandatory
• Resolves from emitted to source file extensions (#​1727, #​1753) @​cspotcode
  • Must enable experimentalResolver, will be enabled by default in a future version (docs)
  • Typechecker requires importing the emitted file extension; ts-node resolves correctly to the source file. E.g. import "./foo.js" will execute foo.ts See also: TypeScript issue #​37582
  • If typechecking is disabled, you can also use source file extensions. E.g. import "./foo.ts"
• Added experimentalSpecifierResolution (#​1727, #​1753) @​cspotcode
  • the same as Node's --experimental-specifier-resolution (Node docs)
  • can also be specified in tsconfig.json for convenience, to avoid the CLI flag
  • allows omitting file extensions in ESM imports, plus a few other CommonJS-style conveniences
• Adds diagnostics property to TSError, with array of TypeScript diagnostic objects from the compiler (API docs) (#​1705, #​1706) @​paulbrimicombe

Changed

• Renames option experimentalResolverFeatures to experimentalResolver (docs) (#​1727) @​cspotcode
• Internal change to ESM loader for compatibility with forthcoming node versions: returns shortCircuit: true (#​1714, #​1715) @​cspotcode
• Performance: Optimize filesystem stat calls in ESM loader and new CommonJS resolver (#​1758, #​1759) @​cspotcode
• Performance, maintenance: Upgrade source-mapper dependency "@​cspotcode/source-map-support"
  • Switches to "trace-mapping" for underlying source-map parsing (#​1729) @​cspotcode

Fixed

• Fixed bug where REPL .type command was not showing any type information when using TypeScript nightly builds (#​1761, #​1762) @​cspotcode
• Correctly suppress "Custom ESM Loaders" warning on newer node versions where the warning's prose changed (#​1701) @​cspotcode
• Fixed REPL bug where function signatures could not be entered across multiple lines (#​1667, #​1677) @​d9k
• REPL treats unparenthesized object literals as objects, instead of as block scopes (#​1697, #​1699) @​jhmaster2000
• Fixed bug where preferTsExts combined with third-party transpiler hooks could disrupt nyc code coverage (#​1755) @​cspotcode
• Fixed bug where file:// URLs in stack traces did not always use percent-encoding (#​1738, #​1726, #​1729) @​cspotcode
• Fixed bug where v8-compile-cache-lib did not correctly unhook itself (#​1717, #​1718, #​1719) @​cspotcode
  • This internal dependency is used to speed up loading the TypeScript compiler

Docs

• Many docs improvements (#​1682) @​cspotcode
• Options page: each option its own linkable header w/usage example (#​1606) @​cspotcode
• Categorize APIs in typedoc, make entrypoints more prominent (#​1456) @​cspotcode
• Clarify that the shorthand for --project is -P, not -p (#​1731, #​1734) @​lobsterkatie
• Add common ESM errors to Troubleshooting page (#​1607) @​cspotcode

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

v10.7.0

Compare Source

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

Added

• Adds --esm flag, option, and ts-node-esm binary (#​1258, #​1655)
  • Enables full esm support; no need for --loader nor NODE_OPTIONS
  • Use shebang #!/usr/bin/env ts-node-esm, run ts-node --esm, or add to your tsconfig.json: "ts-node": {"esm": true}

Changed

• Unflag ESM json modules on node >=17.5.0 (#​1661, #​1665) @​Jamesernator
  • no longer requires --experimental-json-modules
• Lazy-load dependencies to improve startup responsiveness. (#​1676)

Fixed

• Fixed bug where "compiler", "transpiler", and swc backend would not resolve relative to the tsconfig.json that declared them (#​1662, #​1655)
  • Enables reusable tsconfig.json shared via node module to include necessary dependencies

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

v10.6.0

Compare Source

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

Added

• Adds workaround for extensionless entrypoints with ESM loader (#​1649, #​1654)
  • You can now combine tools such as mocha with --loader ts-node/esm, where previously node would throw [ERR_UNKNOWN_FILE_EXTENSION]
  • node has a bug where combining --loader with an extensionless entrypoint causes this error nodejs/node#​33226
  • Some tools, for example mocha, have an extensionless entrypoint. (source, source)
  • Combining NODE_OPTIONS=--loader ts-node/esm with these tools causes this error. mochajs/mocha#​4645
  • node intends to fix this bug in a future release: nodejs/node#​41711
  • In the interim, we have implemented a workaround in ts-node.
• Adds support for target "ES2022" in moduleTypes overrides (#​1650)

Fixed

• Fixed bug where --swc and other third-party transpilers did not respect moduleTypes overrides (#​1651, #​1652, #​1660)
• Fixed bug where node flags were not preserved correctly in process.execArgv (#​1657, #​1658)
  • This affected child_process.fork(), since it uses process.execArgv to create a similar child runtime.
  • With this fix, child_process.fork() will preserve both node flags and ts-node hooks.
• Fixed compatibility TypeScript 4.7's API changes (#​1647, #​1648)

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

v10.5.0

Compare Source

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

Added

• Eliminate "Emit Skipped" errors (#​693, #​1345, #​1629)
  • Avoids all "Emit Skipped" errors by performing a fallback transpileOnly-style transformation.
  • Does not affect typechecking. Type errors are still detected and thrown.
  • Fallback has the same limitations as isolatedModules. This will only affect rare cases such as using const enums with preserveConstEnums disabled.
  • Fixes #​693
• Graduate swc transpiler out of experimental; add swc: true convenience option (docs) (#​1487, #​1536, #​1613, #​1627)
  • "swc": true or --swc will use swc for faster execution
  • This feature is no longer marked "experimental." Thank you to everyone who filed bugs!
• swc transpiler attempts to load @swc/core or @swc/wasm dependencies from your project before falling-back to global installations (#​1613, #​1627)
  • global fallback only occurs when using a global installation of ts-node
• Add support for TypeScript's traceResolution output (docs) (#​1128, #​1491) @​TheUnlocked
• Support import assertions in ESM loader (docs) (#​1557, #​1558, #​1559, #​1573) @​Pokute, @​geigerzaehler
  • Allows importing JSON files from ESM with the requisite flag (docs)
• ts-node -vvv also logs absolute paths to ts-node and typescript, to make it more obvious when you're accidentally using globally-installed versions (#​1323, #​1620)
• Add swc target "es2022" (#​1535, #​1540)
  • When you have target es2022 in tsconfig, will use swc's es2022 target

Changed

• Initialize TypeScript compiler before starting REPL prompt (#​1498) @​TheUnlocked
  • Improves responsiveness for first line of REPL input
• Use v8-compile-cache-lib to load typescript
  • improves startup time (#​1339, #​1603)
• Support both --camelCase and --hyphen-case for all CLI flags; update documentation to use --camelCase (#​1598, #​1599)
  • Not a breaking change; CLI continues to accept both forms
• Make TSError diagnosticText property non-enumerable to prevent it from being logged below the stack (#​1632)

Fixed

• Fix #​1538: REPL inputs fail to transpile via swc (#​1538, #​1541, #​1602)
• Fix #​1478: REPL erroneously logged undefined for all inputs after the first when using swc transpiler (#​1478, #​1580, #​1602)
• Fix #​1389: In --showConfig output, emit accurate moduleTypes paths resolved relative to the tsconfig.json which declared them (#​1389, #​1619)
• Fix: Remove indentation from ts-node --help output (#​1597, #​1600)
• Fix #​1425: Merged definitions correctly into tsconfig.schemastore-schema.json (#​1425, #​1618)
• Fix: Allow disabling "use strict" emit in SWC transpiler (#​1531, #​1537)
• Fix: Add missing ERR_UNKNOWN_FILE_EXTENSION constructor; was throwing ERR_UNKNOWN_FILE_EXTENSION is not a constructor (#​1562) @​bluelovers
• Fix #​1565: entrypoint resolution failed on node v12.0.x and v12.1.x (#​1565, #​1566) @​davidmurdoch

Docs

• Explain env -S flag for shebangs (docs) (#​1448, #​1545) @​sheeit, @​chee
• Suggest skipIgnore when you want to compile files in node_modules (docs) (#​1553) @​webstrand
• Fix typo in moduleTypes on options page (docs) (#​1630, #​1633)

Misc

• Adds experimental experimentalResolverFeatures option, but it does not do anything yet (#​1514, #​1614)

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

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

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

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

---

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