dev-cli
dev-cli copied to clipboard
chore(deps-dev): bump ts-node from 9.1.1 to 10.7.0
Bumps ts-node from 9.1.1 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
--esmflag, option, andts-node-esmbinary (#1258, #1655)
- Enables full
esmsupport; no need for--loadernorNODE_OPTIONS- Use shebang
#!/usr/bin/env ts-node-esm, runts-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
mochawith--loader ts-node/esm, where previously node would throw[ERR_UNKNOWN_FILE_EXTENSION]- node has a bug where combining
--loaderwith 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/esmwith 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
moduleTypesoverrides (#1650)Fixed
- Fixed bug where
--swcand other third-party transpilers did not respectmoduleTypesoverrides (#1651, #1652, #1660)- Fixed bug where node flags were not preserved correctly in
process.execArgv(#1657, #1658)
- This affected
child_process.fork(), since it usesprocess.execArgvto create a similar child runtime.- With this fix,
child_process.fork()will preserve both node flags andts-nodehooks.- 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
v10.5.0
... (truncated)
Commits
f5b6e2d10.7.029a15bcupdate api-extractor reporte842c11Rebuild readme for 10.7.02163398Merge docs into main for 10.7.00792067ts-node-esm/--esmto spawn a child process; decouple config loading fro...f35a120lazy-load dependencies to improve responsiveness when they aren't used (#1676)20cbbf5Allow json modules to be resolved in Node >=17.5.0 without flag (#1665)30f03e110.6.04e1af52update apiextractor report prior to the release of 10.6.089bde51Issue #1651 followup (#1660)- Additional commits viewable in compare view
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 rebasewill rebase this PR -
@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it -
@dependabot mergewill merge this PR after your CI passes on it -
@dependabot squash and mergewill squash and merge this PR after your CI passes on it -
@dependabot cancel mergewill cancel a previously requested merge and block automerging -
@dependabot reopenwill reopen this PR if it is closed -
@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)