Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jan 19, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
imports-loader ^0.8.0 -> ^5.0.0 age adoption passing confidence

Release Notes

webpack-contrib/imports-loader (imports-loader)

v5.0.0

Compare Source

⚠ BREAKING CHANGES
4.0.1 (2022-08-12)
Bug Fixes

v4.0.1

Compare Source

v4.0.0

Compare Source

⚠ BREAKING CHANGES
  • minimum supported Node.js version is 14.15.0
3.1.1 (2021-11-01)
Bug Fixes

v3.1.1

Compare Source

v3.1.0

Compare Source

Features
3.0.1 (2021-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

v2.0.0

Compare Source

⚠ BREAKING CHANGES
  • minimum supported webpack version is 5
  • inline syntax was changed: [] is no longer supported (i.e. imports-loader?imports[]=default|jquery|$&imports[]=angular!./example.js), please use , comma separator (i.e. imports-loader?imports=default|jquery|$,angular!./example.js)

v1.2.0

Compare Source

Features

v1.1.0

Compare Source

Features
  • "|" character can be used as delimiter for inline string syntax (00697de)

v1.0.0

Compare Source

⚠ BREAKING CHANGES
  • minimum supported Node.js version is 10.13
  • minimum supported webpack version is 4
  • inline syntax was changed, please read
  • list of imported modules moved to the imports option, please read
  • wrapper moved to the wrapper option, please read
  • custom variables moved to the additionalCode option, please read
  • generates ES module default import by default (import Foo from 'foo';)
Features
  • validate options
  • support webpack 5
  • implemented the type option (imports can be CommonsJS or ES module format)
  • implemented the ability to generate multiple import in CommonJS or ES module format
  • improved support of inline usage
  • allowed to adding arguments for wrapper
  • allowed to inject any custom code
Bug Fixes
  • do not crash on invalid inline syntax
  • respect 'use strict';

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 renovate bot added the dependencies Pull requests that update a dependency file label Jan 19, 2024
@renovate
Copy link
Contributor Author

renovate bot commented Jan 19, 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/imports-loader
npm ERR!   imports-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_51_585Z-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_51_585Z-debug-0.log

@renovate renovate bot force-pushed the renovate/imports-loader-5.x branch from c1662bd to d2df66a Compare February 11, 2025 00:31
@renovate
Copy link
Contributor Author

renovate bot commented Feb 11, 2025

⚠️ 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: [email protected]
npm error Found: [email protected]
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 [email protected]
npm error node_modules/imports-loader
npm error   imports-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_31_00_668Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2025-02-11T00_31_00_668Z-debug-0.log

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.

1 participant