[Snyk] Upgrade ts-node from 10.3.0 to 10.9.2 #71
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.
Snyk has created this PR to upgrade ts-node from 10.3.0 to 10.9.2.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
The recommended version is 11 versions ahead of your current version.
The recommended version was released a year ago.
Issues fixed by the recommended upgrade:
SNYK-JS-LODASH-1040724
SNYK-JS-MOMENT-2440688
SNYK-JS-SEQUELIZE-2959225
SNYK-JS-SEQUELIZE-3324088
SNYK-JS-DOTTIE-3332763
SNYK-JS-MOMENT-2944238
SNYK-JS-VALIDATOR-1090599
SNYK-JS-VALIDATOR-1090601
SNYK-JS-VALIDATOR-1090602
SNYK-JS-LODASH-1018905
SNYK-JS-SEQUELIZE-3324089
SNYK-JS-SEQUELIZE-3324090
SNYK-JS-SEQUELIZE-2932027
Release notes
Package name: ts-node
Fixed
tsconfig.jsonfile not found on latest TypeScript version (#2091)Fixed
--esm--esmare unaffectedv10.9.0...v10.9.1
https://github.com/TypeStrong/ts-node/milestone/18?closed=1
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) @ cspotcodev10.8.2...v10.9.0
https://github.com/TypeStrong/ts-node/milestone/16?closed=1
Fixed
nyccode coverage reports had incorrect pathsv10.8.1...v10.8.2
https://github.com/TypeStrong/ts-node/milestone/15?closed=1
Fixed
v10.8.0...v10.8.1
https://github.com/TypeStrong/ts-node/milestone/14
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) @ lobsterkatiev10.7.0...v10.8.0
https://github.com/TypeStrong/ts-node/milestone/12
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
v10.6.0...v10.7.0
https://github.com/TypeStrong/ts-node/milestone/11
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.v10.5.0...v10.6.0
https://github.com/TypeStrong/ts-node/milestone/9
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) @ TheUnlocked