fix(deps): update dependency exports-loader to v5 - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
exports-loader	^0.7.0 -> ^5.0.0

---

Release Notes

webpack-contrib/exports-loader (exports-loader)

v5.0.0

Compare Source

⚠ BREAKING CHANGES

• minimum supported Node.js version is 18.12.0 (#​146) (0c658f1)

v4.0.0

Compare Source

⚠ BREAKING CHANGES

• minimum supported Node.js version is 14.15.0

v3.1.0

Compare Source

Features

• output helpful descriptions and links on errors (#​66) (ba96dda)

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 (#​58) (9176392)
• inline syntax was changed: [] is no longer supported (i.e. exports-loader?exports[]=myVariable&exports[]=myFunction!./file.js), please use , (i.e. exports-loader?exports=myVariable,myFunction!./file.js)
• removed filename template support for export names and aliases (i.e. [name]) due unstable behaviour in some cases and very rarely used

1.1.1 (2020-10-09)

Chore

• update schema-utils

v1.1.1

Compare Source

v1.1.0

Compare Source

Features

• "|" character can be used as delimiter for inline string syntax (#​46) (e0bc930)

v1.0.1

Compare Source

Bug Fixes

• better error reporting (#​44) (0397393)

v1.0.0

Compare Source

⚠ BREAKING CHANGES

• minimum supported Node.js version is 10.13
• minimum supported webpack version is 4
• exports values moved to the exports option, please read
• generates ES module named exports by default (exports { Foo })
• multiple exports in the inline syntax were changed, please read

Features

• validate options
• support webpack 5
• implemented the type option (exports can be CommonsJS or ES module format)
• exports can be described using a string or an object value
• implemented the ability to generate multiple experts
• improved support of inline usage

Bug Fixes

• export is not used anymore for CommonJS module format

---

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 was generated by Mend Renovate. View the repository job log.

[renovate]

⚠ 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: scratch-blocks@1.1.0
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.0.0" from exports-loader@5.0.0
npm ERR! node_modules/exports-loader
npm ERR!   exports-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-01-19T16_05_39_716Z-eresolve-report.txt

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

[renovate]

⚠️ 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 warn cli npm v11.1.0 does not support Node.js v18.20.6. This version of npm supports the following node versions: `^20.17.0 || >=22.9.0`. You can find the latest version at https://nodejs.org/.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: scratch-blocks@1.1.206
npm error Found: webpack@4.47.0
npm error node_modules/webpack
npm error   dev webpack@"4.47.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer webpack@"^5.0.0" from exports-loader@5.0.0
npm error node_modules/exports-loader
npm error   exports-loader@"^5.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2025-02-11T00_30_52_607Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2025-02-11T00_30_52_607Z-debug-0.log