marckraw / nestjs-project-template

finance crud build with nestjs
1 stars 0 forks source link

chore(deps-dev): bump ts-node from 10.5.0 to 10.7.0 #12

Closed dependabot[bot] closed 2 years ago

dependabot[bot] commented 2 years ago

Bumps ts-node from 10.5.0 to 10.7.0.

Release notes

Sourced from ts-node's releases.

v10.7.0

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

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

v10.6.0

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

Added

  • Adds workaround for extensionless entrypoints with ESM loader (#1649, #1654)
    • You can now combine tools such as mocha with --loader ts-node/esm, where previously node would throw [ERR_UNKNOWN_FILE_EXTENSION]
    • node has a bug where combining --loader with an extensionless entrypoint causes this error nodejs/node#33226
    • Some tools, for example mocha, have an extensionless entrypoint. (source, source)
    • Combining NODE_OPTIONS=--loader ts-node/esm with these tools causes this error. mochajs/mocha#4645
    • node intends to fix this bug in a future release: nodejs/node#41711
    • In the interim, we have implemented a workaround in ts-node.
  • Adds support for target "ES2022" in moduleTypes overrides (#1650)

Fixed

  • Fixed bug where --swc and other third-party transpilers did not respect moduleTypes overrides (#1651, #1652, #1660)
  • Fixed bug where node flags were not preserved correctly in process.execArgv (#1657, #1658)
    • This affected child_process.fork(), since it uses process.execArgv to create a similar child runtime.
    • With this fix, child_process.fork() will preserve both node flags and ts-node hooks.
  • Fixed compatibility TypeScript 4.7's API changes (#1647, #1648)

https://github.com/TypeStrong/ts-node/compare/v10.5.0...v10.6.0 https://github.com/TypeStrong/ts-node/milestone/9

Commits
  • f5b6e2d 10.7.0
  • 29a15bc update api-extractor report
  • e842c11 Rebuild readme for 10.7.0
  • 2163398 Merge docs into main for 10.7.0
  • 0792067 ts-node-esm / --esm to spawn a child process; decouple config loading fro...
  • f35a120 lazy-load dependencies to improve responsiveness when they aren't used (#1676)
  • 20cbbf5 Allow json modules to be resolved in Node >=17.5.0 without flag (#1665)
  • 30f03e1 10.6.0
  • 4e1af52 update apiextractor report prior to the release of 10.6.0
  • 89bde51 Issue #1651 followup (#1660)
  • Additional commits viewable in compare view


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)