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 loader-utils to v3 #2961

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 17, 2022

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
loader-utils 2.0.4 -> 3.2.1 age adoption passing confidence

Release Notes

webpack/loader-utils

v3.2.1

Compare Source

v3.2.0

Compare Source

Features
  • hash uniformity for base digests (451858b)
3.1.3 (2021-11-04)
Bug Fixes
3.1.2 (2021-11-04)
Bug Fixes
3.1.1 (2021-11-04)
Bug Fixes
  • base64 and unicode characters (02b1f3f)

v3.1.3

Compare Source

v3.1.2

Compare Source

v3.1.1

Compare Source

v3.1.0

Compare Source

Features
  • added md4 (wasm version) and md4-native (crypto module version) algorithms (cbf9d1d)

v3.0.0

Compare Source

⚠ BREAKING CHANGES
  • minimum supported Node.js version is 12.13.0 (93a87ce)
  • use xxhash64 by default for [hash]/[contenthash] and getHashDigest API
  • [emoji] was removed without replacements, please use custom function if you need this
  • removed getOptions in favor loaderContext.getOptions (loaderContext is this inside loader function), note - special query parameters like ?something=true is not supported anymore, if you need this please do it on loader side, but we strongly recommend avoid it, as alternative you can use ?something=1 and handle 1 as true
  • removed getRemainingRequest in favor loaderContext.remainingRequest (loaderContext is this inside loader function)
  • removed getCurrentRequest in favor loaderContext.currentRequest (loaderContext is this inside loader function)
  • removed parseString in favor JSON.parse
  • removed parseQuery in favor new URLSearchParams(loaderContext.resourceQuery.slice(1)) where loaderContext is this in loader function
  • removed stringifyRequest in favor JSON.stringify(loaderContext.utils.contextify(loaderContext.context || loaderContext.rootContext, request)) (loaderContext is this inside loader function), also it will be cachable and faster
  • isUrlRequest ignores only absolute URLs and #hash requests, data URI and root relative request are handled as requestable due webpack v5 support them
Bug Fixes
  • allowed the interpolateName API works without options (862ea7d)

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.

@codeclimate
Copy link

codeclimate bot commented Dec 17, 2022

Code Climate has analyzed commit a0ff26c and detected 0 issues on this pull request.

The test coverage on the diff in this pull request is 100.0% (85% is the threshold).

This pull request will bring the total coverage in the repository to 96.6% (0.0% change).

View more on Code Climate.

@renovate renovate bot changed the title Update dependency loader-utils to v3 chore(deps): update dependency loader-utils to v3 Dec 17, 2022
@mattseddon mattseddon closed this Dec 17, 2022
@mattseddon mattseddon deleted the renovate/loader-utils-3.x branch December 17, 2022 21:10
@renovate
Copy link
Contributor Author

renovate bot commented Dec 17, 2022

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 3.x releases. But if you manually upgrade to 3.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

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.

1 participant