chore(deps): update dependency ts-node to v10.9.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
ts-node (source)	10.8.2 -> 10.9.1

---

Release Notes

TypeStrong/ts-node

v10.9.1

Compare Source

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

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

v10.9.0

Compare Source

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

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

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ 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.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[renovate]

⚠ Artifact update problem

Renovate failed to update artifacts 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:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: sample/33-graphql-mercurius/package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: nest-typescript-starter@1.0.0
npm ERR! Found: mercurius@12.2.0
npm ERR! node_modules/mercurius
npm ERR!   mercurius@"12.2.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer mercurius@"^8.12.0 || ^9.0.0 || ^10.0.0" from @nestjs/mercurius@10.2.1
npm ERR! node_modules/@nestjs/mercurius
npm ERR!   @nestjs/mercurius@"10.2.1" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/worker/ff8743/cafb3d/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/worker/ff8743/cafb3d/cache/others/npm/_logs/2023-06-13T07_05_58_085Z-debug-0.log

File name: sample/13-mongo-typeorm/package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: typeorm@0.3.16
npm ERR! Found: mongodb@3.6.0
npm ERR! node_modules/mongodb
npm ERR!   mongodb@"3.6.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peerOptional mongodb@"^5.2.0" from typeorm@0.3.16
npm ERR! node_modules/typeorm
npm ERR!   typeorm@"0.3.16" from the root project
npm ERR!   peer typeorm@"^0.3.0" from @nestjs/typeorm@9.0.1
npm ERR!   node_modules/@nestjs/typeorm
npm ERR!     @nestjs/typeorm@"9.0.1" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: mongodb@5.6.0
npm ERR! node_modules/mongodb
npm ERR!   peerOptional mongodb@"^5.2.0" from typeorm@0.3.16
npm ERR!   node_modules/typeorm
npm ERR!     typeorm@"0.3.16" from the root project
npm ERR!     peer typeorm@"^0.3.0" from @nestjs/typeorm@9.0.1
npm ERR!     node_modules/@nestjs/typeorm
npm ERR!       @nestjs/typeorm@"9.0.1" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/worker/ff8743/cafb3d/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/worker/ff8743/cafb3d/cache/others/npm/_logs/2023-06-13T07_07_59_839Z-debug-0.log