ngx-fileupload
ngx-fileupload copied to clipboard
chore(deps): update dependency ts-node to v10.9.2
This PR contains the following updates:
Package | Change | Age | Adoption | Passing | Confidence |
---|---|---|---|---|---|
ts-node (source) | 10.8.1 -> 10.9.2 |
Release Notes
TypeStrong/ts-node (ts-node)
v10.9.2
: Fix tsconfig.json
file not found
Fixed
- Fixed
tsconfig.json
file not found on latest TypeScript version (https://github.com/TypeStrong/ts-node/pull/2091)
v10.9.1
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
- Only affects projects on node >=18.6.0 using
https://github.com/TypeStrong/ts-node/milestone/18?closed=1
v10.9.0
Added
-
--project
accepts path to a directory containing atsconfig.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
v10.8.2
Fixed
- Revert "Use file URL for source map paths" (#1821) @cspotcode
- 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
https://github.com/TypeStrong/ts-node/milestone/15?closed=1
Configuration
📅 Schedule: Branch creation - "after 10pm every weekday,before 5am every weekday,every weekend" in timezone Europe/Berlin, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ 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 was generated by Mend Renovate. View the repository job log.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
Comparison is base (
adf4a2c
) 98.95% compared to head (2c07fb6
) 98.95%.
Additional details and impacted files
@@ Coverage Diff @@
## development #747 +/- ##
============================================
Coverage 98.95% 98.95%
============================================
Files 12 12
Lines 287 287
Branches 53 53
============================================
Hits 284 284
Partials 3 3
Flag | Coverage Δ | |
---|---|---|
core | 98.95% <ø> (ø) |
Flags with carried forward coverage won't be shown. Click here to find out more.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
⚠ Artifact update problem
Renovate failed to update an artifact 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: src/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: @angular-devkit/[email protected]
npm ERR! node_modules/@angular-devkit/core
npm ERR! @angular-devkit/core@"14.0.3" from the root project
npm ERR! @angular-devkit/core@"14.0.3" from @angular-devkit/[email protected]
npm ERR! node_modules/@angular-devkit/build-angular
npm ERR! dev @angular-devkit/build-angular@"14.0.3" from the root project
npm ERR! 3 more (@angular-devkit/schematics, @angular/cli, @schematics/angular)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @angular-devkit/core@"^9.0.0 || ^10.0.0 || ^11.0.0 || ^12.0.0 || ^13.0.0" from [email protected]
npm ERR! node_modules/angular-cli-ghpages
npm ERR! dev angular-cli-ghpages@"1.0.0" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: @angular-devkit/[email protected]
npm ERR! node_modules/@angular-devkit/core
npm ERR! peer @angular-devkit/core@"^9.0.0 || ^10.0.0 || ^11.0.0 || ^12.0.0 || ^13.0.0" from [email protected]
npm ERR! node_modules/angular-cli-ghpages
npm ERR! dev angular-cli-ghpages@"1.0.0" 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!
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2023-12-08T12_33_34_458Z-eresolve-report.txt
npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2023-12-08T12_33_34_458Z-debug-0.log