Update dependency ts-node to v10.9.1 #27
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
10.2.1
->10.9.1
Release Notes
TypeStrong/ts-node (ts-node)
v10.9.1
Compare Source
Fixed
--esm
--esm
are unaffectedhttps://github.com/TypeStrong/ts-node/milestone/18?closed=1
v10.9.0
Compare Source
Added
--project
accepts path to a directory containing atsconfig.json
(#1829, #1830) @cspotcodeexperimentalTsImportSpecifiers
option which allows using voluntary.ts
file extensions in import specifiers (undocumented except for API docs) (#1815) @cspotcodeFixed
child_process.fork()
would erroneously execute the parent's entrypoint script, not the intended child script (#1812, #1814) @devversion"react-jsx"
and"react-jsxdev"
in swc transpiler (#1800, #1802) @cspotcoderepl.evalCode()
with code not ending in a newline would not update the typechecker accordingly (#1764, #1824) @cspotcodehttps://github.com/TypeStrong/ts-node/milestone/16?closed=1
v10.8.2
Compare Source
Fixed
nyc
code coverage reports had incorrect pathshttps://github.com/TypeStrong/ts-node/milestone/15?closed=1
v10.8.1
Compare Source
Fixed
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
module=NodeNext
,module=Node16
,.mts
,.cts
,.mjs
, and.cjs
file extensions (#1414, #1694, #1744, #1745, #1727, #1717, #1753, #1757) @cspotcodeexperimentalResolver
(docs)experimentalResolver
, will be enabled by default in a future version (docs)import "./foo.js"
will executefoo.ts
See also: TypeScript issue #37582import "./foo.ts"
experimentalSpecifierResolution
(#1727, #1753) @cspotcode--experimental-specifier-resolution
(Node docs)tsconfig.json
for convenience, to avoid the CLI flagdiagnostics
property toTSError
, with array of TypeScript diagnostic objects from the compiler (API docs) (#1705, #1706) @paulbrimicombeChanged
experimentalResolverFeatures
toexperimentalResolver
(docs) (#1727) @cspotcodeshortCircuit: true
(#1714, #1715) @cspotcodeFixed
.type
command was not showing any type information when using TypeScript nightly builds (#1761, #1762) @cspotcodepreferTsExts
combined with third-party transpiler hooks could disruptnyc
code coverage (#1755) @cspotcodefile://
URLs in stack traces did not always use percent-encoding (#1738, #1726, #1729) @cspotcodeDocs
--project
is-P
, not-p
(#1731, #1734) @lobsterkatiehttps://github.com/TypeStrong/ts-node/milestone/12
v10.7.0
Compare Source
Questions about this release? Ask in the official discussion thread: #1680
Added
--esm
flag, option, andts-node-esm
binary (#1258, #1655)esm
support; no need for--loader
norNODE_OPTIONS
#!/usr/bin/env ts-node-esm
, runts-node --esm
, or add to your tsconfig.json:"ts-node": {"esm": true}
Changed
--experimental-json-modules
Fixed
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
mocha
with--loader ts-node/esm
, where previously node would throw[ERR_UNKNOWN_FILE_EXTENSION]
--loader
with an extensionless entrypoint causes this error nodejs/node#33226mocha
, have an extensionless entrypoint. (source, source)NODE_OPTIONS=--loader ts-node/esm
with these tools causes this error. mochajs/mocha#4645moduleTypes
overrides (#1650)Fixed
--swc
and other third-party transpilers did not respectmoduleTypes
overrides (#1651, #1652, #1660)process.execArgv
(#1657, #1658)child_process.fork()
, since it usesprocess.execArgv
to create a similar child runtime.child_process.fork()
will preserve both node flags andts-node
hooks.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
transpileOnly
-style transformation.isolatedModules
. This will only affect rare cases such as usingconst enums
withpreserveConstEnums
disabled.swc: true
convenience option (docs) (#1487, #1536, #1613, #1627)"swc": true
or--swc
will use swc for faster execution@swc/core
or@swc/wasm
dependencies from your project before falling-back to global installations (#1613, #1627)traceResolution
output (docs) (#1128, #1491) @TheUnlockedts-node -vvv
also logs absolute paths tots-node
andtypescript
, to make it more obvious when you're accidentally using globally-installed versions (#1323, #1620)Changed
v8-compile-cache-lib
to load typescript--camelCase
and--hyphen-case
for all CLI flags; update documentation to use--camelCase
(#1598, #1599)TSError
diagnosticText
property non-enumerable to prevent it from being logged below the stack (#1632)Fixed
undefined
for all inputs after the first when using swc transpiler (#1478, #1580, #1602)--showConfig
output, emit accuratemoduleTypes
paths resolved relative to thetsconfig.json
which declared them (#1389, #1619)ts-node --help
output (#1597, #1600)tsconfig.schemastore-schema.json
(#1425, #1618)"use strict"
emit in SWC transpiler (#1531, #1537)ERR_UNKNOWN_FILE_EXTENSION
constructor; was throwingERR_UNKNOWN_FILE_EXTENSION is not a constructor
(#1562) @blueloversDocs
env -S
flag for shebangs (docs) (#1448, #1545) @sheeit, @cheeskipIgnore
when you want to compile files in node_modules (docs) (#1553) @webstrandmoduleTypes
on options page (docs) (#1630, #1633)Misc
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
Changed
creatEsmHooks
(API docs) (#1506, #1529)Fixed
https://github.com/TypeStrong/ts-node/milestone/8
v10.3.1
Compare Source
Fixed
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
util.promisify(setTimeout)(1000)
orfs.readFileSync('example.txt')
createEsmHooks()
function to create ESM loader hooks (API docs) (#1439) @nonararegister()
accepts a ts-nodeService
(API docs) (#1474)register(options)
is still supported; no breaking changes--emit
to--help
output (#1400, #1484) @markbradley27Changed
require('source-map-support')
, they will be redirected to@cspotcode/source-map-support
Fixed
source-map-support
instead of@cspotcode/source-map-support
(#1440, #1441, #1438, #1495, cspotcode/node-source-map-support#23, #1496, #1497) @ejose19require('source-map-support')
, they will be redirected to@cspotcode/source-map-support
@cspotcode/source-map-support
for the fixes and enhancements listed here:@cspotcode/source-map-support
changelog100
on first line and* 2
on second line would erronously be interpreted as100 * 2
allowJs
(#1488, #1489)TS_NODE_IGNORE
andTS_NODE_IGNORE_DIAGNOSTICS
; treat empty environment variable as empty array (#1301, #1483) @ValeriaVGTS_NODE_IGNORE= ts-node ./example.ts
will disable default ignore rules; will compile files in./node_modules
Docs
https://github.com/TypeStrong/ts-node/milestone/5
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.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.