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

chore(deps): update dependency expose-loader to v5 #4198

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 20, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
expose-loader 1.0.3 -> 5.0.0 age adoption passing confidence

Release Notes

webpack-contrib/expose-loader (expose-loader)

v5.0.0

Compare Source

⚠ BREAKING CHANGES

v4.1.0

Compare Source

Features
  • added globalObject option to modify global context (#​205) (1ad9096)

v4.0.0

Compare Source

⚠ BREAKING CHANGES
  • minimum supported Node.js version is 14.15.0

v3.1.0

Compare Source

Features
Bug Fixes

v3.0.0

Compare Source

⚠ BREAKING CHANGES
  • minimum supported Node.js version is 12.13.0

v2.0.0

Compare Source

⚠ BREAKING CHANGES
  • minimum supported webpack version is 5
  • inline syntax was changed: [] is no longer supported (i.e. import $ from "expose-loader?exposes[]=$&exposes[]=jQuery!jquery), please use , comma separator (i.e. import $ from "expose-loader?exposes=$,jQuery!jquery)
1.0.3 (2020-11-26)
Bug Fixes
1.0.2 (2020-11-25)
Bug Fixes
  • don't strip loader "ref" from import string (6271fc4)
1.0.1 (2020-10-09)
Chore
  • update schema-utils

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: Never, 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.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Jan 20, 2024
Copy link
Contributor Author

renovate bot commented Jan 20, 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: [email protected]
npm ERR! Found: [email protected]
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.0.0" from [email protected]
npm ERR! node_modules/expose-loader
npm ERR!   dev expose-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! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2024-02-28T18_18_45_637Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-02-28T18_18_45_637Z-debug-0.log

@renovate renovate bot force-pushed the renovate/expose-loader-5.x branch from bbbd1ff to 70d2294 Compare February 28, 2024 18:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants