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 terser-webpack-plugin to v5 #245

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 14, 2020

This PR contains the following updates:

Package Type Update Change
terser-webpack-plugin devDependencies major ^4.2.3 -> ^5.0.0

Release Notes

webpack-contrib/terser-webpack-plugin

v5.0.3

Compare Source

v5.0.2

Compare Source

v5.0.1

Compare Source

v5.0.0

Compare Source

⚠ BREAKING CHANGES
  • webpack@4 no longer supported
  • removed the cache option
  • removed the cacheKeys option
  • removed the sourceMap option (respect the devtool option by default)
Bug Fixes
  • reduce deps
  • performance improvement
4.2.3 (2020-10-07)
Bug Fixes
4.2.2 (2020-09-19)
Bug Fixes
4.2.1 (2020-09-15)
Bug Fixes

Renovate configuration

📅 Schedule: 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 WhiteSource Renovate. View repository job log here.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling 43452a0 on renovate/terser-webpack-plugin-5.x into b9476f0 on develop.

@renovate renovate bot force-pushed the renovate/terser-webpack-plugin-5.x branch from 43452a0 to 1c50534 Compare October 15, 2020 22:36
@renovate renovate bot force-pushed the renovate/terser-webpack-plugin-5.x branch from 1c50534 to 022b1e6 Compare October 28, 2020 00:35
@renovate
Copy link
Contributor Author

renovate bot commented Oct 28, 2020

⚠️ 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 check 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 old lockfile 
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile 
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile 
npm WARN old lockfile Error: Integrity checksum failed when using sha512: wanted sha512-mqAC2r1NDmRjG+z3KCJ/i61tycKlmADIjxnDhQab+KBxSAGbF/W7/zwB2guy/ypIeKrrftNsIYkNZZQKf3vJcg== but got sha512-s7PoyDv/II1ObgQunCbB9PdLmUcBZcnWOcxDh7O0N/UwDEsHyqkW+Qh28jW+mVuCdx7gLB0BotYI1Y6uI9iyew==.
npm WARN old lockfile     at /usr/local/node/15.0.1/lib/node_modules/npm/node_modules/pacote/lib/registry.js:123:39
npm WARN old lockfile     at async Array.<anonymous> (/usr/local/node/15.0.1/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:591:9)
npm WARN old lockfile  Could not fetch metadata for [email protected] Error: Integrity checksum failed when using sha512: wanted sha512-mqAC2r1NDmRjG+z3KCJ/i61tycKlmADIjxnDhQab+KBxSAGbF/W7/zwB2guy/ypIeKrrftNsIYkNZZQKf3vJcg== but got sha512-s7PoyDv/II1ObgQunCbB9PdLmUcBZcnWOcxDh7O0N/UwDEsHyqkW+Qh28jW+mVuCdx7gLB0BotYI1Y6uI9iyew==.
npm WARN old lockfile     at /usr/local/node/15.0.1/lib/node_modules/npm/node_modules/pacote/lib/registry.js:123:39
npm WARN old lockfile     at async Array.<anonymous> (/usr/local/node/15.0.1/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:591:9) {
npm WARN old lockfile   code: 'EINTEGRITY'
npm WARN old lockfile }
npm WARN old lockfile Error: Integrity checksum failed when using sha512: wanted sha512-mqAC2r1NDmRjG+z3KCJ/i61tycKlmADIjxnDhQab+KBxSAGbF/W7/zwB2guy/ypIeKrrftNsIYkNZZQKf3vJcg== but got sha512-s7PoyDv/II1ObgQunCbB9PdLmUcBZcnWOcxDh7O0N/UwDEsHyqkW+Qh28jW+mVuCdx7gLB0BotYI1Y6uI9iyew==.
npm WARN old lockfile     at /usr/local/node/15.0.1/lib/node_modules/npm/node_modules/pacote/lib/registry.js:123:39
npm WARN old lockfile     at async Array.<anonymous> (/usr/local/node/15.0.1/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:591:9)
npm WARN old lockfile  Could not fetch metadata for [email protected] Error: Integrity checksum failed when using sha512: wanted sha512-mqAC2r1NDmRjG+z3KCJ/i61tycKlmADIjxnDhQab+KBxSAGbF/W7/zwB2guy/ypIeKrrftNsIYkNZZQKf3vJcg== but got sha512-s7PoyDv/II1ObgQunCbB9PdLmUcBZcnWOcxDh7O0N/UwDEsHyqkW+Qh28jW+mVuCdx7gLB0BotYI1Y6uI9iyew==.
npm WARN old lockfile     at /usr/local/node/15.0.1/lib/node_modules/npm/node_modules/pacote/lib/registry.js:123:39
npm WARN old lockfile     at async Array.<anonymous> (/usr/local/node/15.0.1/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:591:9) {
npm WARN old lockfile   code: 'EINTEGRITY'
npm WARN old lockfile }
npm WARN old lockfile Error: Integrity checksum failed when using sha512: wanted sha512-5GCgdeevIXwR3cW4Qj5XWC5MO1iSCz8+IPn0mMw6awAt/PBiey8yyO7MhePRsaMqghJAhg6Q3QLYWSnUHWkG6A== but got sha512-7PtVymN48hGcO4fGjybyBSIWDsLU4H4XlvOHfq91pz9kkGlonzwTfYkaIEwiRg/dAJF9YlbsduBAgtYLi+8cFg==.
npm WARN old lockfile     at /usr/local/node/15.0.1/lib/node_modules/npm/node_modules/pacote/lib/registry.js:123:39
npm WARN old lockfile     at async Array.<anonymous> (/usr/local/node/15.0.1/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:591:9)
npm WARN old lockfile  Could not fetch metadata for [email protected] Error: Integrity checksum failed when using sha512: wanted sha512-5GCgdeevIXwR3cW4Qj5XWC5MO1iSCz8+IPn0mMw6awAt/PBiey8yyO7MhePRsaMqghJAhg6Q3QLYWSnUHWkG6A== but got sha512-7PtVymN48hGcO4fGjybyBSIWDsLU4H4XlvOHfq91pz9kkGlonzwTfYkaIEwiRg/dAJF9YlbsduBAgtYLi+8cFg==.
npm WARN old lockfile     at /usr/local/node/15.0.1/lib/node_modules/npm/node_modules/pacote/lib/registry.js:123:39
npm WARN old lockfile     at async Array.<anonymous> (/usr/local/node/15.0.1/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:591:9) {
npm WARN old lockfile   code: 'EINTEGRITY'
npm WARN old lockfile }
npm WARN old lockfile Error: Integrity checksum failed when using sha512: wanted sha512-oWjZFGMc0q2ak+8OxdmMffS79LIT0UEtmpV4h1/AARvESIqqKljf8mrfP+dQ2kas7XttsAZIxRBuWu7Y5JH8KQ== but got sha512-ArmIS8w+XhL4KGP05kxMousA9SFxmeirMkNNcVe5LjK4iGCbZ8qKnG4byuXMru7Ty7a9QwiMUIf80X+zmJuf2A==.
npm WARN old lockfile     at /usr/local/node/15.0.1/lib/node_modules/npm/node_modules/pacote/lib/registry.js:123:39
npm WARN old lockfile     at async Array.<anonymous> (/usr/local/node/15.0.1/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:591:9)
npm WARN old lockfile  Could not fetch metadata for [email protected] Error: Integrity checksum failed when using sha512: wanted sha512-oWjZFGMc0q2ak+8OxdmMffS79LIT0UEtmpV4h1/AARvESIqqKljf8mrfP+dQ2kas7XttsAZIxRBuWu7Y5JH8KQ== but got sha512-ArmIS8w+XhL4KGP05kxMousA9SFxmeirMkNNcVe5LjK4iGCbZ8qKnG4byuXMru7Ty7a9QwiMUIf80X+zmJuf2A==.
npm WARN old lockfile     at /usr/local/node/15.0.1/lib/node_modules/npm/node_modules/pacote/lib/registry.js:123:39
npm WARN old lockfile     at async Array.<anonymous> (/usr/local/node/15.0.1/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:591:9) {
npm WARN old lockfile   code: 'EINTEGRITY'
npm WARN old lockfile }
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: wp-foo-bar@undefined
npm ERR! Found: [email protected]
npm ERR! node_modules/webpack
npm ERR!   dev webpack@"4.44.2" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer webpack@"^5.1.0" from [email protected]
npm ERR! node_modules/terser-webpack-plugin
npm ERR!   dev terser-webpack-plugin@"^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/2020-10-28T00_35_54_113Z-debug.log

@ravichdev
Copy link
Contributor

Related to #242 on upgrade issues to Webpack 5. This package/PR would no longer be required after upgrade to webpack 5 https://github.com/webpack-contrib/terser-webpack-plugin#getting-started

@derekherman derekherman closed this Nov 5, 2020
@derekherman derekherman deleted the renovate/terser-webpack-plugin-5.x branch November 5, 2020 20:18
@renovate
Copy link
Contributor Author

renovate bot commented Nov 5, 2020

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 5.x releases. But if you manually upgrade to 5.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.

4 participants