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.

Sign up for GitHub

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

Jump to bottom

Update dependency webpack-assets-manifest to v5 #878

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

Update dependency webpack-assets-manifest to v5 #878

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Dec 7, 2020 •
edited

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
webpack-assets-manifest ^3.1.1 -> ^5.0.0 age adoption passing confidence

ℹ️ Find our documentation at https://github.com/Financial-Times/next/wiki/Renovate.

Release Notes

webdeveric/webpack-assets-manifest (webpack-assets-manifest)

v5.2.1: 5.2.1

Compare Source

Full Changelog: webdeveric/webpack-assets-manifest@v5.2.0...v5.2.1

v5.2.0: 5.2.0

Compare Source

What's Changed

Full Changelog: webdeveric/webpack-assets-manifest@v5.1.0...v5.2.0

v5.1.0: 5.1.0

Compare Source

  • Improved webpack 5 persistent cache handling
  • Bug fix related to compiler.outputFileSystem when using Jest.
  • Added options.extra. This can hold arbitrary data for use in customize/transform.
  • Updated dependencies
  • Linting fixes

v5.0.6: 5.0.6

Compare Source

  • Added manifest parameter to afterOptions hook.
  • Use manifest parameter in internal transform and afterOptions taps.
  • Check options.enabled after afterOptions hook has been called.

v5.0.5: 5.0.5

Compare Source

Allow options.space to be a string.

v5.0.4: 5.0.4

Compare Source

  • Updated hook being used to process assets.
    Use processAssets hook instead of afterProcessAssets so that async lock/unlock functions can be used.
  • Updated getLockFilename() to use hash of dirname.
  • Removed lockSync and unlockSync functions.
  • Updated min webpack version to 5.2.

v5.0.3: 5.0.3

Compare Source

Use asset.info.hotModuleReplacement to identify HMR files.

v5.0.2: 5.0.2

Compare Source

  • Improved entrypoints handling. #​140
  • Updated inDevServer() to not use WEBPACK_DEV_SERVER / WEBPACK_SERVE env vars. #​125
  • Improved writeToDisk: 'auto' behavior
  • Updated dependencies

v5.0.1: 5.0.1

Compare Source

Fixes for #​115 and #​116

  • Improved finding asset modules
  • Updated hooks for watch mode
  • Use public path with entrypoints
  • Updated dependencies

v5.0.0: 5.0.0

Compare Source

  • Compatible with webpack 5 only (5.1+ required).
  • Supports finding asset modules.
  • Updated options schema to prevent additional properties. This helps with catching typos in option names.
  • ⚠️ Updated default value of the output option to be assets-manifest.json.
    This is to prevent confusion when working with Web app manifests or WebExtension manifests.

v4.0.6: 4.0.6

Compare Source

  • Added manifest parameter to afterOptions hook.
  • Use manifest parameter in internal transform and afterOptions taps.
  • Check options.enabled after afterOptions hook has been called.

v4.0.5: 4.0.5

Compare Source

Allow options.space to be a string.

v4.0.4: 4.0.4

Compare Source

  • Updated getLockFilename() to use hash of dirname.
  • Removed lockSync and unlockSync functions.

v4.0.3: 4.0.3

Compare Source

Use asset.info.hotModuleReplacement to identify HMR files.

v4.0.2: 4.0.2

Compare Source

  • Improved entrypoints handling. #​140
  • Updated inDevServer() to not use WEBPACK_DEV_SERVER / WEBPACK_SERVE env vars. #​125
  • Improved writeToDisk: 'auto' behavior
  • Updated dependencies

v4.0.1: 4.0.1

Compare Source

Fixes for #​115 and #​116

  • Updated hooks for watch mode
  • Use public path with entrypoints
  • Updated dependencies

v4.0.0: 4.0.0

Compare Source

  • Minimum webpack version is now 4.40.0
  • Updated dependencies
  • Added options: enabled, entrypointsUseAssets, contextRelativeKey
  • Use lock files when using writeToDisk and when emitting the manifest
  • Changed writeToDisk to default to auto
  • Swapped the key/value in assetNames
  • Updated merge behavior for entrypoints
  • done hook is now an AsyncSeriesHook
  • Added clear() method to empty the manifest during webpack watch
  • ⚠️ The structure of the entrypoints data has been updated to include preload and prefetch assets. Assets for an entrypoint are now included in an assets property under the entrypoint.

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.

@renovate renovate bot requested a review from a team as a code owner December 7, 2020 22:01
@renovate renovate bot added the dependencies label Dec 7, 2020
Base automatically changed from master to main February 8, 2021 12:49
@renovate renovate bot changed the title Update dependency webpack-assets-manifest to v5 Update dependency webpack-assets-manifest to v5 - autoclosed Apr 6, 2021
@renovate renovate bot closed this Apr 6, 2021
@renovate renovate bot deleted the renovate-webpack-assets-manifest-5.x branch April 6, 2021 16:59
@renovate renovate bot changed the title Update dependency webpack-assets-manifest to v5 - autoclosed Update dependency webpack-assets-manifest to v5 Apr 9, 2021
@renovate renovate bot reopened this Apr 9, 2021
@renovate renovate bot restored the renovate-webpack-assets-manifest-5.x branch April 9, 2021 16:53
@renovate renovate bot force-pushed the renovate-webpack-assets-manifest-5.x branch from a05098e to 3b2ae5b Compare February 23, 2023 14:55
@renovate
Copy link
Author

renovate bot commented Feb 23, 2023

⚠ 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 ERESOLVE overriding peer dependency
npm WARN While resolving: react-docgen-typescript@2.2.2
npm WARN Found: typescript@3.9.5
npm WARN node_modules/typescript
npm WARN   dev typescript@"3.9.5" from the root project
npm WARN   4 more (@storybook/react-docgen-typescript-plugin, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer typescript@">= 4.3.x" from react-docgen-typescript@2.2.2
npm WARN node_modules/@storybook/react-docgen-typescript-plugin/node_modules/react-docgen-typescript
npm WARN   react-docgen-typescript@"^2.1.1" from @storybook/react-docgen-typescript-plugin@1.0.2-canary.6.9d540b91e815f8fc2f8829189deb00553559ff63.0
npm WARN   node_modules/@storybook/react-docgen-typescript-plugin
npm WARN 
npm WARN Conflicting peer dependency: typescript@4.9.5
npm WARN node_modules/typescript
npm WARN   peer typescript@">= 4.3.x" from react-docgen-typescript@2.2.2
npm WARN   node_modules/@storybook/react-docgen-typescript-plugin/node_modules/react-docgen-typescript
npm WARN     react-docgen-typescript@"^2.1.1" from @storybook/react-docgen-typescript-plugin@1.0.2-canary.6.9d540b91e815f8fc2f8829189deb00553559ff63.0
npm WARN     node_modules/@storybook/react-docgen-typescript-plugin
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: @financial-times/dotcom-build-base@0.0.0
npm ERR! Found: webpack@4.46.0
npm ERR! node_modules/webpack
npm ERR!   peer webpack@"^4.39.2" from @financial-times/dotcom-build-base@0.0.0
npm ERR!   packages/dotcom-build-base
npm ERR!     @financial-times/dotcom-build-base@0.0.0
npm ERR!     examples/building-sass-files/node_modules/@financial-times/dotcom-build-base
npm ERR!       dev @financial-times/dotcom-build-base@"file:../../packages/dotcom-build-base" from example-build-sass@undefined
npm ERR!       examples/building-sass-files
npm ERR!         example-build-sass@undefined
npm ERR!         node_modules/example-build-sass
npm ERR!     @financial-times/dotcom-build-base@0.0.0
npm ERR!     examples/dynamic-imports/node_modules/@financial-times/dotcom-build-base
npm ERR!       dev @financial-times/dotcom-build-base@"file:../../packages/dotcom-build-base" from example-dynamic-imports@0.0.0
npm ERR!       examples/dynamic-imports
npm ERR!         example-dynamic-imports@0.0.0
npm ERR!         node_modules/example-dynamic-imports
npm ERR!     @financial-times/dotcom-build-base@0.0.0
npm ERR!     examples/ft-ui/node_modules/@financial-times/dotcom-build-base
npm ERR!       dev @financial-times/dotcom-build-base@"file:../../packages/dotcom-build-base" from example-ft-ui@0.0.0
npm ERR!       examples/ft-ui
npm ERR!         example-ft-ui@0.0.0
npm ERR!         node_modules/example-ft-ui
npm ERR!     @financial-times/dotcom-build-base@0.0.0
npm ERR!     examples/kitchen-sink/node_modules/@financial-times/dotcom-build-base
npm ERR!       dev @financial-times/dotcom-build-base@"file:../../packages/dotcom-build-base" from example-kitchen-sink@0.0.0
npm ERR!       examples/kitchen-sink
npm ERR!         example-kitchen-sink@0.0.0
npm ERR!         node_modules/example-kitchen-sink
npm ERR!     @financial-times/dotcom-build-base@0.0.0
npm ERR!     node_modules/@financial-times/dotcom-build-base
npm ERR!       workspace packages/dotcom-build-base from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer webpack@"^5.2.0" from webpack-assets-manifest@5.1.0
npm ERR! node_modules/webpack-assets-manifest
npm ERR!   webpack-assets-manifest@"^5.0.0" from @financial-times/dotcom-build-base@0.0.0
npm ERR!   packages/dotcom-build-base
npm ERR!     @financial-times/dotcom-build-base@0.0.0
npm ERR!     examples/building-sass-files/node_modules/@financial-times/dotcom-build-base
npm ERR!       dev @financial-times/dotcom-build-base@"file:../../packages/dotcom-build-base" from example-build-sass@undefined
npm ERR!       examples/building-sass-files
npm ERR!     @financial-times/dotcom-build-base@0.0.0
npm ERR!     examples/dynamic-imports/node_modules/@financial-times/dotcom-build-base
npm ERR!       dev @financial-times/dotcom-build-base@"file:../../packages/dotcom-build-base" from example-dynamic-imports@0.0.0
npm ERR!       examples/dynamic-imports
npm ERR!     @financial-times/dotcom-build-base@0.0.0
npm ERR!     examples/ft-ui/node_modules/@financial-times/dotcom-build-base
npm ERR!       dev @financial-times/dotcom-build-base@"file:../../packages/dotcom-build-base" from example-ft-ui@0.0.0
npm ERR!       examples/ft-ui
npm ERR!     @financial-times/dotcom-build-base@0.0.0
npm ERR!     examples/kitchen-sink/node_modules/@financial-times/dotcom-build-base
npm ERR!       dev @financial-times/dotcom-build-base@"file:../../packages/dotcom-build-base" from example-kitchen-sink@0.0.0
npm ERR!       examples/kitchen-sink
npm ERR!     @financial-times/dotcom-build-base@0.0.0
npm ERR!     node_modules/@financial-times/dotcom-build-base
npm ERR!       workspace packages/dotcom-build-base 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/2023-02-23T14_55_00_580Z-debug-0.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
dependencies
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
0 participants