ion-sdk-js
ion-sdk-js copied to clipboard
chore(deps): update dependency ts-loader to v9
This PR contains the following updates:
Package | Change | Age | Adoption | Passing | Confidence |
---|---|---|---|---|---|
ts-loader | 8.0.12 -> 9.4.2 |
Release Notes
TypeStrong/ts-loader
v9.4.2
v9.4.1
-
Hotfix: Disable
enhanced-resolve
- thanks @manuth
v9.4.0
v9.3.1
- Bug fix: Generate declaration files for js files if allowJs is set to true [#1260] - thanks @hediet and @mvilliger
v9.3.0
v9.2.9
v9.2.8
v9.2.7
- cater for change in resolveTypeReferenceDirective API in TypeScript 4.7 [#1421] - thanks @johnny_reilly and @cspotcode for inspiration in ts-node work here: https://github.com/TypeStrong/ts-node/pull/1648
v9.2.6
v9.2.5
v9.2.4
v9.2.3
v9.2.2
- Start consuming webpack loader types - thanks @johnnyreilly
- Add webpack minimum version in peerDependencies - thanks @afdev82
v9.2.1
v9.2.0
- Fixed impossibility to have several instances of ts-loader with different compiler options - thanks @timocov
v9.1.2
v9.1.1
v9.1.0
- Use caches for module resolution and type reference directives when using compiler default functions - thanks @sheetalkamat - uses: https://github.com/microsoft/TypeScript/pull/43700
v9.0.2
v9.0.1
v9.0.0
Breaking changes:
- minimum webpack version: 5
- minimum node version: 12
Changes:
v8.4.0
- fix: cater for change in resolveTypeReferenceDirective API in 4.7 - thanks @dragomirtitian
- This is a backport from v9.2.7 for webpack 4 compatibility
v8.3.0
- Fixed impossibility to have several instances of ts-loader with different compiler options - thanks @timocov
- This is a backport from v9.2.0 for webpack 4 compatibility
v8.2.0
- Use caches for module resolution and type reference directives when using compiler default functions - thanks @sheetalkamat - uses: https://github.com/microsoft/TypeScript/pull/43700
- This is a backport from v9.1.0 for webpack 4 compatibility
v8.1.0
v8.0.18
v8.0.17
v8.0.16
v8.0.15
- Update definition files in watch mode in webpack@5 - thanks @appzuka,@JonWallsten,@alexander-akait
- Add afterDeclarations to getCustomTransformers in README.md - thanks @appzuka
v8.0.14
-
Upgrade
chalk
,loader-utils
, andsemver
to latest stable versions - thanks Avi Vahl
v8.0.13
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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 has been generated by Mend Renovate. View repository job log 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 check 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: package-lock.json
npm WARN old lockfile
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/webpack
npm ERR! dev webpack@"4.44.2" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer webpack@"^5.0.0" from [email protected]
npm ERR! node_modules/ts-loader
npm ERR! dev ts-loader@"9.2.2" 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/renovate-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/renovate-cache/others/npm/_logs/2021-05-22T18_43_51_670Z-debug.log
⚠ 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: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/webpack
npm ERR! dev webpack@"^4.44.2" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer webpack@"^5.0.0" from [email protected]
npm ERR! node_modules/ts-loader
npm ERR! dev ts-loader@"9.4.2" 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-03-16T15_43_22_523Z-eresolve-report.txt
npm ERR! A complete log of this run can be found in:
npm ERR! /tmp/renovate-cache/others/npm/_logs/2023-03-16T15_43_22_523Z-debug-0.log