Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dependency source-map-loader to v5 #889

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 12, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
source-map-loader ^1.1.3 -> ^5.0.0 age adoption passing confidence

Release Notes

webpack-contrib/source-map-loader (source-map-loader)

v5.0.0

Compare Source

⚠ BREAKING CHANGES
4.0.2 (2023-12-27)
Bug Fixes
4.0.1 (2022-10-07)
Bug Fixes
  • logic when sourceRoot contains absolute URL (e724a1f)

v4.0.2

Compare Source

v4.0.1

Compare Source

v4.0.0

Compare Source

⚠ BREAKING CHANGES
  • minimum supported Node.js version is 14.15.0
3.0.1 (2022-01-03)
Chore
  • update source-map-js

v3.0.2

Compare Source

3.0.2 (2022-10-21)
Bug Fixes

v3.0.1

Compare Source

v3.0.0

Compare Source

⚠ BREAKING CHANGES
  • minimum supported Node.js version is 12.13.0
2.0.2 (2021-05-17)
Bug Fixes
  • don't ignore source file when sourceContent contains null (#​148) (8ec2b86)
2.0.1 (2021-02-10)
Bug Fixes
  • switch from source-map to source-map-js package (perf increase)
  • fix watch with invalid sourceURL

v2.0.2

Compare Source

v2.0.1

Compare Source

v2.0.0

Compare Source

⚠ BREAKING CHANGES
  • minimum supported webpack version is 5
1.1.3 (2020-12-04)
Bug Fixes
1.1.2 (2020-10-27)
Bug Fixes
  • do not watch unnecessary sources (23768df)
1.1.1 (2020-10-09)
Chore
  • update schema-utils

Configuration

📅 Schedule: Branch creation - "before 6am" in timezone Europe/London, 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.

Copy link
Contributor Author

renovate bot commented May 12, 2024

⚠️ 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: lag@undefined
npm ERR! Found: webpack@4.47.0
npm ERR! node_modules/webpack
npm ERR!   dev webpack@"^4.47.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer webpack@"^5.72.1" from source-map-loader@5.0.0
npm ERR! node_modules/source-map-loader
npm ERR!   dev source-map-loader@"^5.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! 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/2024-05-12T00_42_17_523Z-debug-0.log

Copy link

vercel bot commented May 12, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
lag-xdwa ❌ Failed (Inspect) May 12, 2024 0:42am

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants