[Snyk] Upgrade ts-node from 10.7.0 to 10.9.2

[HaLaGu1L]

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:

	Issue	Score	Exploit Maturity
	Regular Expression Denial of Service (ReDoS) SNYK-JS-GETFUNCNAME-5923417	176	Proof of Concept
	Cross-site Scripting (XSS) SNYK-JS-SERIALIZEJAVASCRIPT-6147607	176	Proof of Concept

Release notes

Package name: ts-node

• 10.9.2 - 2023-12-08
  

  Fixed

  • Fixed tsconfig.json file not found on latest TypeScript version (#2091)
• 10.9.1 - 2022-07-14
  

  Fixed

  • Workaround nodejs bug introduced in 18.6.0 (#1838) @ cspotcode
    • Only affects projects on node >=18.6.0 using --esm
    • Older versions of node and projects without --esm are unaffected

  v10.9.0...v10.9.1
  https://github.com/TypeStrong/ts-node/milestone/18?closed=1

• 10.9.0 - 2022-07-13
  

  Added

  • --project accepts path to a directory containing a tsconfig.json (#1829, #1830) @ cspotcode
    • previously it required an explicit filename
  • Added helpful error message when swc version is too old to support our configuration (#1802) @ cspotcode
  • Added experimentalTsImportSpecifiers option which allows using voluntary .ts file extensions in import specifiers (undocumented except for API docs) (#1815) @ cspotcode

  Fixed

  • Fixed bug where child_process.fork() would erroneously execute the parent's entrypoint script, not the intended child script (#1812, #1814) @ devversion
  • Fixed support for jsx modes "react-jsx" and "react-jsxdev" in swc transpiler (#1800, #1802) @ cspotcode
  • Fixed support for import assertions in swc transpiler (#1817, #1802) @ cspotcode
  • Fixed bug where calling repl.evalCode() with code not ending in a newline would not update the typechecker accordingly (#1764, #1824) @ cspotcode

  v10.8.2...v10.9.0
  https://github.com/TypeStrong/ts-node/milestone/16?closed=1

• 10.8.2 - 2022-07-02
  

  Fixed

  • Revert "Use file URL for source map paths" (#1821) @ cspotcode
    • Fixes #1790: ts-node 10.8.1 regression where nyc code coverage reports had incorrect paths
    • 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

  v10.8.1...v10.8.2
  https://github.com/TypeStrong/ts-node/milestone/15?closed=1

• 10.8.1 - 2022-06-03
  

  Fixed

  • 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

  v10.8.0...v10.8.1
  https://github.com/TypeStrong/ts-node/milestone/14

• 10.8.0 - 2022-05-21
  

  Questions about this release? Ask in the official discussion thread: #1767

  Added

  • Added support for module=NodeNext, module=Node16, .mts, .cts, .mjs, and .cjs file extensions (#1414, #1694, #1744, #1745, #1727, #1717, #1753, #1757) @ cspotcode
    • For best results, enable experimentalResolver (docs)
    • 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 experimentalResolver, will be enabled by default in a future version (docs)
    • Typechecker requires importing the emitted file extension; ts-node resolves correctly to the source file. E.g. import "./foo.js" will execute foo.ts See also: TypeScript issue #37582
    • If typechecking is disabled, you can also use source file extensions. E.g. import "./foo.ts"
  • Added experimentalSpecifierResolution (#1727, #1753) @ cspotcode
    • the same as Node's --experimental-specifier-resolution (Node docs)
    • can also be specified in tsconfig.json for convenience, to avoid the CLI flag
    • allows omitting file extensions in ESM imports, plus a few other CommonJS-style conveniences
  • Adds diagnostics property to TSError, with array of TypeScript diagnostic objects from the compiler (API docs) (#1705, #1706) @ paulbrimicombe

  Changed

  • Renames option experimentalResolverFeatures to experimentalResolver (docs) (#1727) @ cspotcode
  • Internal change to ESM loader for compatibility with forthcoming node versions: returns shortCircuit: true (#1714, #1715) @ cspotcode
  • 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

  • Fixed bug where REPL .type command was not showing any type information when using TypeScript nightly builds (#1761, #1762) @ cspotcode
  • 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 preferTsExts combined with third-party transpiler hooks could disrupt nyc code coverage (#1755) @ cspotcode
  • Fixed bug where file:// URLs in stack traces did not always use percent-encoding (#1738, #1726, #1729) @ cspotcode
  • 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

  Docs

  • 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 --project is -P, not -p (#1731, #1734) @ lobsterkatie
  • Add common ESM errors to Troubleshooting page (#1607) @ cspotcode

  v10.7.0...v10.8.0
  https://github.com/TypeStrong/ts-node/milestone/12

• 10.7.0 - 2022-03-06
  

  Questions about this release? Ask in the official discussion thread: #1680

  Added

  • Adds --esm flag, option, and ts-node-esm binary (#1258, #1655)
    • Enables full esm support; no need for --loader nor NODE_OPTIONS
    • Use shebang #!/usr/bin/env ts-node-esm, run ts-node --esm, or add to your tsconfig.json: "ts-node": {"esm": true}

  Changed

  • Unflag ESM json modules on node >=17.5.0 (#1661, #1665) @ Jamesernator
    • no longer requires --experimental-json-modules
  • Lazy-load dependencies to improve startup responsiveness. (#1676)

  Fixed

  • 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

  v10.6.0...v10.7.0
  https://github.com/TypeStrong/ts-node/milestone/11

from ts-node GitHub release notes

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• This PR was automatically created by Snyk using the credentials of a real user.
• Max score is 1000. Note that the real score may have changed since the PR was raised.

---

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:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

[coderabbitai]

Important

Review skipped

Ignore keyword(s) in the title.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

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?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

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)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.