chore(deps): update dependency ts-node to v10 #135
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
2 times, most recently
from
8c8baa2 to
4a6a4b8
Compare
renovate
bot
force-pushed
the
renovate/ts-node-10.x
branch
from
4a6a4b8 to
e238954
Compare
renovate
bot
force-pushed
the
renovate/ts-node-10.x
branch
from
e238954 to
ca098d7
Compare
renovate
bot
force-pushed
the
renovate/ts-node-10.x
branch
from
ca098d7 to
99b5332
Compare
renovate
bot
force-pushed
the
renovate/ts-node-10.x
branch
from
99b5332 to
770a670
Compare
renovate
bot
force-pushed
the
renovate/ts-node-10.x
branch
from
770a670 to
6416d44
Compare
renovate
bot
force-pushed
the
renovate/ts-node-10.x
branch
from
6416d44 to
3f893da
Compare
⚠ 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:
8.10.2->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
v10.4.0Compare Source
Added
Changed
creatEsmHooks(API docs) (#1506, #1529)Fixed
https://github.com/TypeStrong/ts-node/milestone/8
v10.3.1Compare Source
Fixed
https://github.com/TypeStrong/ts-node/milestone/7
v10.3.0Compare 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--emitto--helpoutput (#1400, #1484) @markbradley27Changed
require('source-map-support'), they will be redirected to@cspotcode/source-map-supportFixed
source-map-supportinstead 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-supportfor the fixes and enhancements listed here:@cspotcode/source-map-supportchangelog100on first line and* 2on second line would erronously be interpreted as100 * 2allowJs(#1488, #1489)TS_NODE_IGNOREandTS_NODE_IGNORE_DIAGNOSTICS; treat empty environment variable as empty array (#1301, #1483) @ValeriaVGTS_NODE_IGNORE= ts-node ./example.tswill disable default ignore rules; will compile files in./node_modulesDocs
https://github.com/TypeStrong/ts-node/milestone/5
v10.2.1Compare Source
Fixed
https://github.com/TypeStrong/ts-node/milestone/6
v10.2.0Compare Source
Questions about this release? Ask in the official discussion thread: #1423
Added
--no-experimental-repl-await,experimentalReplAwait, orTS_NODE_EXPERIMENTAL_REPL_AWAIT(CLI docs, API docs)"pretty": falsedisables pretty formatting of diagnostics even when stdout is a TTY (#1418, #1420) @elevatebartprettyoption, not to be confused with TypeScript'sprettyoptionconst foo = 1in the REPL,foois unused. We ignore the resulting diagnosticfoo is declared but its value is never readFixed
--loaderasyncannotations (#1405, #1410)require.resolveerror when@types/nodepeerDependency is missing (#1419, #1422)https://github.com/TypeStrong/ts-node/milestone/2
v10.1.0Compare Source
Questions about this release? Ask in the official discussion thread: #1390
Added
"moduleType"option to override module type -- CommonJS or ECMAScript -- on select files. (docs) (#1342, #1371, #1376)webpack.config.ts, must execute as CommonJS but the rest of the project is ESMpackage.json"type"andtsconfig.json"module".cjsand.mjsextensions, but for.tsand.tsxfiles"extends"support for"ts-node"options intsconfig.json(#1328, #1356)"ts-node": {}options will be parsed from extended tsconfigsscopeandscopeDir; add both to CLI andtsconfig.jsonoptions; un-deprecateTS_NODE_SCOPEenv var; addTS_NODE_SCOPE_DIRenv var (docs) (#1346, #1367)Changed
"ts-node"object at the top of--showConfigoutput instead of the bottom (#1355)Fixed
[stdin],[eval], and<repl>contexts (#1333)ts-node -e__filename,__dirname,moduleand sub-fields ofmodule,exports, and builtin module aliasesfs, etckeepClassNamestotrue(#1344)Docs
node --loader ts-node/esm(docs) (#1379)https://github.com/TypeStrong/ts-node/milestone/3
v10.0.0Compare Source
Questions about this release? Ask in the official discussion thread: #1337
Breaking changes are prefixed with [BREAKING]
Added
--show-configto log the resolved configuration (docs) (#1100, #1243)swcintegration and new--transpileroption to use third-party transpilers for a massive speed boost on large codebases (docs) (#779, #1160)scopeDirAPI option (docs) (#1155)projectSearchDirAPI option (docs) (#1155)--cwd-modeandts-node-cwdto resolve config file relative to cwd, not entrypoint script (#1155)Changed
--script-modedefault behavior; resolve tsconfig relative to entrypoint script instead of cwd (#949, #1197, #1155)$PATH, becausets-nodewill respect the script's localtsconfig.json--cwd-modeorts-node-cwdif you need legacy behaviorignorerules evaluate relative totsconfig.jsondirectory, otherwisecwd(#1155)--dirto--cwd; renameTS_NODE_DIRtoTS_NODE_CWD(#1155)--dirandTS_NODE_DIRare deprecated but still parsed for backwards-compatibility--direffectively changed the working directory ofts-node; renaming makes this behavior more obviousDeprecated
TS_NODE_SCOPE(#1155)--dirandTS_NODE_DIR(#1155)Removed
DEFAULTS,normalizeSlashes,parse,splitts-node's programmatic APIFixed
ERR_REQUIRE_ESMwhen attempting to execute ESM as CJS, even when not using--loader ts-node/esm(#1232)nodecompileris loaded relative totsconfig.jsoninstead of entrypoint script (#1155)ts-node ./indexmay execute the wrong file extension because tsconfig search poisons therequire.resolvecache (#1155)Docs
CONTRIBUTING.mdto document the codebase and our development workflowhttps://github.com/TypeStrong/ts-node/milestone/1
v9.1.1Compare Source
No code changes. We re-packed and republished v9.1.1, because the v9.1.0 package was broken due to an npm v7 bug.
Fixes
v9.1.0Compare Source
Added
--typeCheckflag to override--transpileOnlyflag specified intsconfig.json(#1142)Changed
RegistertoService. It is still aliased asRegisterfor backwards compatibility (#1158)Fixed
--es-module-specifier-resolutionas an alias of--experimental-specifier-resolutionfor node 12 compatibility (#1122) @nguyensomniacDocs
ts-node-devin README (#1131) @iamandrewlucatransformersdescription to clarify incompatibility withtranspileOnly(#1123)Misc
v9.0.0Compare Source
Breaking changes are labelled [BREAKING] below.
Added
ERR_REQUIRE_ESMwhen a file isrequire()d which should be loaded as ESM (#1031)"exports"declaration to package.json in backwards-compatible way, enablingnode --loader ts-node/esmwithout file extension (#1028)"require"option via tsconfig (#925)NODE_NO_READLINEenvironment variable (#1090)node --loader ts-node/esm/transpile-only(#1102) @concisionChanged
Fixed
realpath, which should fix workflows that use symlinks, such aspnpm, Lerna workspaces, or other mono-repo configurations (#970)node_moduleswhen--skip-ignoreor--ignoreoptions are configured to allow it (#970)getSourceFileNames/rootNames(#999)projectVersionevery timegetSourceFileNameschanges, avoiding accidentally outdated typechecking (#998)ts.transpileModule(#1054) @thetutlage--experimental-specifier-resolutioncoming fromNODE_OPTIONSin ESM loader (#1085) @evg656e.cjs,.mjs, and any unexpected file extensions (#1103) @concisionDocs
Misc
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.