[Snyk] Upgrade ts-node from 10.8.1 to 10.9.2 #4
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.8.1 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 4 versions ahead of your current version.
The recommended version was released on 9 months ago.
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
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
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: