Update dependency ts-node to v10.9.2 #10
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/ts-node-10.x
branch
from
b3d37c6 to
575238d
Compare
|
👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎ This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored. |
renovate
bot
force-pushed
the
renovate/ts-node-10.x
branch
from
575238d to
eedb733
Compare
renovate
bot
force-pushed
the
renovate/ts-node-10.x
branch
from
eedb733 to
56dd23d
Compare
renovate
bot
changed the title
⚠ Artifact update problemRenovate 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:
The artifact failure details are included below: File name: pnpm-lock.yaml |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.4.0->10.9.2Release Notes
TypeStrong/ts-node (ts-node)
v10.9.2: Fixtsconfig.jsonfile not foundCompare Source
Fixed
tsconfig.jsonfile not found on latest TypeScript version (https://github.com/TypeStrong/ts-node/pull/2091)v10.9.1Compare Source
Fixed
--esm--esmare unaffectedhttps://github.com/TypeStrong/ts-node/milestone/18?closed=1
v10.9.0Compare Source
Added
--projectaccepts path to a directory containing atsconfig.json(#1829, #1830) @cspotcodeexperimentalTsImportSpecifiersoption which allows using voluntary.tsfile 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.2Compare Source
Fixed
nyccode coverage reports had incorrect pathshttps://github.com/TypeStrong/ts-node/milestone/15?closed=1
v10.8.1Compare Source
Fixed
https://github.com/TypeStrong/ts-node/milestone/14
v10.8.0Compare Source
Questions about this release? Ask in the official discussion thread: #1767
Added
module=NodeNext,module=Node16,.mts,.cts,.mjs, and.cjsfile 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.tsSee also: TypeScript issue #37582import "./foo.ts"experimentalSpecifierResolution(#1727, #1753) @cspotcode--experimental-specifier-resolution(Node docs)tsconfig.jsonfor convenience, to avoid the CLI flagdiagnosticsproperty toTSError, with array of TypeScript diagnostic objects from the compiler (API docs) (#1705, #1706) @paulbrimicombeChanged
experimentalResolverFeaturestoexperimentalResolver(docs) (#1727) @cspotcodeshortCircuit: true(#1714, #1715) @cspotcodeFixed
.typecommand was not showing any type information when using TypeScript nightly builds (#1761, #1762) @cspotcodepreferTsExtscombined with third-party transpiler hooks could disruptnyccode coverage (#1755) @cspotcodefile://URLs in stack traces did not always use percent-encoding (#1738, #1726, #1729) @cspotcodeDocs
--projectis-P, not-p(#1731, #1734) @lobsterkatiehttps://github.com/TypeStrong/ts-node/milestone/12
v10.7.0Compare Source
Questions about this release? Ask in the official discussion thread: #1680
Added
--esmflag, option, andts-node-esmbinary (#1258, #1655)esmsupport; no need for--loadernorNODE_OPTIONS#!/usr/bin/env ts-node-esm, runts-node --esm, or add to your tsconfig.json:"ts-node": {"esm": true}Changed
--experimental-json-modulesFixed
https://github.com/TypeStrong/ts-node/milestone/11
v10.6.0Compare Source
Questions about this release? Ask in the official discussion thread: #1666
Added
mochawith--loader ts-node/esm, where previously node would throw[ERR_UNKNOWN_FILE_EXTENSION]--loaderwith an extensionless entrypoint causes this error nodejs/node#33226mocha, have an extensionless entrypoint. (source, source)NODE_OPTIONS=--loader ts-node/esmwith these tools causes this error. mochajs/mocha#4645moduleTypesoverrides (#1650)Fixed
--swcand other third-party transpilers did not respectmoduleTypesoverrides (#1651, #1652, #1660)process.execArgv(#1657, #1658)child_process.fork(), since it usesprocess.execArgvto create a similar child runtime.child_process.fork()will preserve both node flags andts-nodehooks.https://github.com/TypeStrong/ts-node/milestone/9
v10.5.0Compare 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 enumswithpreserveConstEnumsdisabled.swc: trueconvenience option (docs) (#1487, #1536, #1613, #1627)"swc": trueor--swcwill use swc for faster execution@swc/coreor@swc/wasmdependencies from your project before falling-back to global installations (#1613, #1627)traceResolutionoutput (docs) (#1128, #1491) @TheUnlockedts-node -vvvalso logs absolute paths tots-nodeandtypescript, to make it more obvious when you're accidentally using globally-installed versions (#1323, #1620)Changed
v8-compile-cache-libto load typescript--camelCaseand--hyphen-casefor all CLI flags; update documentation to use--camelCase(#1598, #1599)TSErrordiagnosticTextproperty non-enumerable to prevent it from being logged below the stack (#1632)Fixed
undefinedfor all inputs after the first when using swc transpiler (#1478, #1580, #1602)--showConfigoutput, emit accuratemoduleTypespaths resolved relative to thetsconfig.jsonwhich declared them (#1389, #1619)ts-node --helpoutput (#1597, #1600)tsconfig.schemastore-schema.json(#1425, #1618)"use strict"emit in SWC transpiler (#1531, #1537)ERR_UNKNOWN_FILE_EXTENSIONconstructor; was throwingERR_UNKNOWN_FILE_EXTENSION is not a constructor(#1562) @blueloversDocs
env -Sflag for shebangs (docs) (#1448, #1545) @sheeit, @cheeskipIgnorewhen you want to compile files in node_modules (docs) (#1553) @webstrandmoduleTypeson options page (docs) (#1630, #1633)Misc
experimentalResolverFeaturesoption, but it does not do anything yet (#1514, #1614)https://github.com/TypeStrong/ts-node/milestone/4
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 was generated by Mend Renovate. View the repository job log.