[Snyk] Upgrade ts-node from 10.7.0 to 10.9.2 #9
Conversation
This file contains hidden or 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
Snyk has created this PR to upgrade ts-node from 10.7.0 to 10.9.2. See this package in npm: ts-node See this project in Snyk: https://app.snyk.io/org/halagu1l/project/05706aca-db5b-4f39-aa0f-17df53b62c8d?utm_source=github&utm_medium=referral&page=upgrade-pr
|
Important Review skippedIgnore keyword(s) in the title. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
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.
Snyk has created this PR to upgrade ts-node from 10.7.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 6 versions ahead of your current version.
The recommended version was released on a year ago.
Issues fixed by the recommended upgrade:
SNYK-JS-GETFUNCNAME-5923417
SNYK-JS-SERIALIZEJAVASCRIPT-6147607
Release notes
Package name: ts-node
-
10.9.2 - 2023-12-08
- Fixed
-
10.9.1 - 2022-07-14
- Workaround nodejs bug introduced in 18.6.0 (#1838) @ cspotcode
- Only affects projects on node >=18.6.0 using
- Older versions of node and projects without
-
10.9.0 - 2022-07-13
- previously it required an explicit filename
- Added helpful error message when swc version is too old to support our configuration (#1802) @ cspotcode
- Added
- Fixed bug where
- Fixed support for jsx modes
- Fixed support for import assertions in swc transpiler (#1817, #1802) @ cspotcode
- Fixed bug where calling
-
10.8.2 - 2022-07-02
- Revert "Use file URL for source map paths" (#1821) @ cspotcode
- Fixes #1790: ts-node 10.8.1 regression where
- 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
-
10.8.1 - 2022-06-03
- 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
-
10.8.0 - 2022-05-21
- Added support for
- For best results, enable
- 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
- Typechecker requires importing the emitted file extension; ts-node resolves correctly to the source file. E.g.
- If typechecking is disabled, you can also use source file extensions. E.g.
- Added
- the same as Node's
- can also be specified in
- allows omitting file extensions in ESM imports, plus a few other CommonJS-style conveniences
- Adds
- Renames option
- Internal change to ESM loader for compatibility with forthcoming node versions: returns
- 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 bug where REPL
- 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
- Fixed bug where
- 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
- 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
- Add common ESM errors to Troubleshooting page (#1607) @ cspotcode
-
10.7.0 - 2022-03-06
- Adds
- Enables full
- Use shebang
- Unflag ESM json modules on node >=17.5.0 (#1661, #1665) @ Jamesernator
- no longer requires
- Lazy-load dependencies to improve startup responsiveness. (#1676)
- 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
from ts-node GitHub release notesFixed
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
Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information: