Skip to content

Update dependency webpack-cli to v5#485

Closed
renovate[bot] wants to merge 1 commit intomainfrom
renovate/webpack-cli-5.x
Closed

Update dependency webpack-cli to v5#485
renovate[bot] wants to merge 1 commit intomainfrom
renovate/webpack-cli-5.x

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Nov 17, 2022

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
webpack-cli (source) ^3.3.12 -> ^5.1.4 age adoption passing confidence

Release Notes

webpack/webpack-cli (webpack-cli)

v5.1.4

Compare Source

Bug Fixes
  • multi compiler progress output (f659624)

v5.1.3

Compare Source

Bug Fixes

v5.1.2

Compare Source

Bug Fixes
  • improve check for custom webpack and webpack-dev-server package existance (0931ab6)
  • improve help for some flags (f468614)
  • improved support for .cts and .mts extensions (a77daf2)

v5.1.1

Compare Source

Bug Fixes

v5.1.0

Compare Source

Features
Performance Improvements

5.0.2 (2023-04-21)

Bug Fixes
  • error message for missing default export in configuration (#​3685) (e0a4a09)
  • perf: reduced startup time (3b79059)

5.0.1 (2022-12-05)

Bug Fixes

v5.0.2

Compare Source

Bug Fixes
  • error message for missing default export in configuration (#​3685) (e0a4a09)
  • perf: reduced startup time (3b79059)

v5.0.1

Compare Source

Bug Fixes

v5.0.0

Compare Source

Bug Fixes
Features
  • failOnWarnings option (#​3317) (c48c848)
  • update commander to v9 (#​3460) (6621c02)
  • added the --define-process-env-node-env option
  • update interpret to v3 and rechoir to v0.8
  • add an option for preventing interpret (#​3329) (c737383)
BREAKING CHANGES
  • the minimum supported webpack version is v5.0.0 (#​3342) (b1af0dc), closes #​3342
  • webpack-cli no longer supports webpack v4, the minimum supported version is webpack v5.0.0
  • webpack-cli no longer supports webpack-dev-server v3, the minimum supported version is webpack-dev-server v4.0.0
  • remove the migrate command (#​3291) (56b43e4), closes #​3291
  • remove the --prefetch option in favor the PrefetchPlugin plugin
  • remove the --node-env option in favor --define-process-env-node-env
  • remove the --hot option in favor of directly using the HotModuleReplacement plugin (only for build command, for serve it will work)
  • the behavior logic of the --entry option has been changed - previously it replaced your entries, now the option adds a specified entry, if you want to return the previous behavior please use webpack --entry-reset --entry './src/my-entry.js'

v4.10.0

Compare Source

Bug Fixes
Features

4.9.2 (2022-01-24)

Bug Fixes

4.9.1 (2021-10-18)

Bug Fixes

v4.9.2

Compare Source

Bug Fixes

v4.9.1

Compare Source

Bug Fixes

v4.9.0

Compare Source

Bug Fixes
Features
  • allow to run commands without webpack installation where it is unnecessary (#​2907) (603041d)

v4.8.0

Compare Source

Bug Fixes
Features
  • show possible values for option in help output (#​2819) (828e5c9)
  • init-generator: add ability to specify a package manager of choice (#​2769) (e53f164)

4.7.2 (2021-06-07)

Note: Version bump only for package webpack-cli (due @webpack-cli/serve)

4.7.1 (2021-06-07)

Bug Fixes

v4.7.2

Compare Source

Note: Version bump only for package webpack-cli (due @webpack-cli/serve)

v4.7.1

Compare Source

Bug Fixes

v4.7.0

Compare Source

Bug Fixes
Features

v4.6.0

Compare Source

Bug Fixes
Features

v4.5.0

Compare Source

Notes
  • now you can use webpack.config.mjs and webpack.config.js with { "type": "module" } in package.json
  • you can avoid using the cross-env package:

Before:

{
  "scripts": {
    "build": "cross-env NODE_ENV=production webpack --config build/webpack.config.js"
  }
}

Now (you can remove the cross-env if you don't use it somewhere else):

{
  "scripts": {
    "build": "webpack --node-env=production --config build/webpack.config.js"
  }
}
  • the mode option respect the --node-env option if you don't set the mode option explicit using CLI options or in configuration(s), i.e. --node-env production set process.env.NODE_ENV and mode to production
Bug Fixes
Features

v4.4.0

Compare Source

Bug Fixes
Features

4.3.1 (2020-12-31)

Bug Fixes

v4.3.1

Compare Source

Bug Fixes

v4.3.0

Compare Source

Bug Fixes
  • fix problems with --mode and config resolution, there are situations when we resolve an invalid config file, the --mode option does not affect on config resolution, if you faced with an error after updating, please use the --config option
  • correct usage of cli-flags (#​2205) (c8fc7d1)
  • defer setting default mode to core (#​2095) (3eb410e)
  • respect the --watch-options-stdin option (2d1e001)
  • respect --color/--no-color option (#​2042) (09bd812)
  • stringify stats using streaming approach (#​2190) (9bf4e92)
  • use logger for error with proper exit code (#​2076) (2c9069f)
  • reduce spammy logs (#​2206) (9b3cc28)
  • respect the infrastructureLogging.level option (logger uses stderr) (#​2144) (7daccc7)
  • respect all options from command line for the server command
  • help and version output
  • respect stats from the config (webpack@4) (#​2098) (2d6e5c6)
  • fixed colors work with multi compiler mode (webpack@4)
Features
  • add bundle command (alias for webpack [options])
  • add pnpm support for package installation (#​2040) (46cba36)

v4.2.0

Compare Source

Bug Fixes
Features

v4.1.0

Compare Source

Bug Fixes
Features

v4.0.0

Compare Source

Bug Fixes
Features
  • assign config paths in build dependencies in cache config (#​1900) (7e90f11)

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
Copy link
Contributor Author

renovate bot commented Nov 17, 2022

⚠ 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 notice 
npm notice New major version of npm available! 8.19.4 -> 9.7.1
npm notice Changelog: <https://github.com/npm/cli/releases/tag/v9.7.1>
npm notice Run `npm install -g npm@9.7.1` to update!
npm notice 
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: react-final-form-generator@1.4.0
npm ERR! Found: webpack@4.44.1
npm ERR! node_modules/webpack
npm ERR!   webpack@"4" from @storybook/builder-webpack4@6.5.16
npm ERR!   node_modules/@storybook/builder-webpack4
npm ERR!     @storybook/builder-webpack4@"6.5.16" from @storybook/core-server@6.5.16
npm ERR!     node_modules/@storybook/core-server
npm ERR!       @storybook/core-server@"6.5.16" from @storybook/core@6.5.16
npm ERR!       node_modules/@storybook/core
npm ERR!         @storybook/core@"6.5.16" from @storybook/react@6.5.16
npm ERR!         node_modules/@storybook/react
npm ERR!   peer webpack@"*" from @storybook/core@6.5.16
npm ERR!   node_modules/@storybook/core
npm ERR!     @storybook/core@"6.5.16" from @storybook/react@6.5.16
npm ERR!     node_modules/@storybook/react
npm ERR!       dev @storybook/react@"^6.5.16" from the root project
npm ERR!   21 more (@storybook/core-client, @storybook/core-common, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! dev webpack-cli@"^5.1.4" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: webpack@5.86.0
npm ERR! node_modules/webpack
npm ERR!   peer webpack@"5.x.x" from webpack-cli@5.1.4
npm ERR!   node_modules/webpack-cli
npm ERR!     dev webpack-cli@"^5.1.4" 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/worker/6b8bfb/9360a0/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/worker/6b8bfb/9360a0/cache/others/npm/_logs/2023-06-07T21_21_14_774Z-debug-0.log

@renovate renovate bot force-pushed the renovate/webpack-cli-5.x branch from 4d62c0e to c9d38ae Compare December 5, 2022 20:45
@stale
Copy link

stale bot commented Apr 13, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix This will not be worked on label Apr 13, 2023
@renovate renovate bot force-pushed the renovate/webpack-cli-5.x branch from c9d38ae to 7d9e33f Compare April 21, 2023 17:44
@renovate renovate bot force-pushed the renovate/webpack-cli-5.x branch 2 times, most recently from 885d29f to 2890d22 Compare May 9, 2023 14:32
@renovate renovate bot force-pushed the renovate/webpack-cli-5.x branch 2 times, most recently from a4438d5 to 6f82d61 Compare June 4, 2023 18:52
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate renovate bot force-pushed the renovate/webpack-cli-5.x branch from 6f82d61 to bb5315f Compare June 7, 2023 21:21
@stale stale bot closed this Dec 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

wontfix This will not be worked on

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants