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

chore(deps): update dependency webpack-cli to v5 #1470

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

chore(deps): update dependency webpack-cli to v5 #1470

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 28, 2023 •
edited

Mend Renovate

This PR contains the following updates:

Package Type Update Change OpenSSF
webpack-cli (source) devDependencies major 3.3.12 -> 5.1.4 OpenSSF Scorecard

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: Enabled.

♻ 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 Mar 28, 2023 •
edited

⚠ 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 v10.5.0 does not support Node.js v16.20.2. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: ci-vs-cd-slides@undefined
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.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! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2024-03-28T03_28_30_167Z-eresolve-report.txt

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

@renovate renovate bot force-pushed the renovate/webpack-cli-5.x branch 13 times, most recently from 713cc15 to 83bd669 Compare April 3, 2023 12:30
@renovate renovate bot force-pushed the renovate/webpack-cli-5.x branch 3 times, most recently from 9570f31 to 63d85e7 Compare April 21, 2023 20:47
@renovate renovate bot force-pushed the renovate/webpack-cli-5.x branch 3 times, most recently from 985d9b2 to 8eed63e Compare May 9, 2023 07:02
@renovate renovate bot force-pushed the renovate/webpack-cli-5.x branch 2 times, most recently from df59225 to 322a069 Compare May 10, 2023 08:54
@renovate renovate bot force-pushed the renovate/webpack-cli-5.x branch 8 times, most recently from 4fabc0e to c3c0183 Compare June 4, 2023 04:14
@renovate renovate bot force-pushed the renovate/webpack-cli-5.x branch 6 times, most recently from 3d12964 to ad85851 Compare September 11, 2023 07:54
@renovate renovate bot force-pushed the renovate/webpack-cli-5.x branch 2 times, most recently from a01f430 to 7e21144 Compare September 17, 2023 06:27
@renovate renovate bot force-pushed the renovate/webpack-cli-5.x branch 10 times, most recently from 458722e to 209cd9e Compare October 10, 2023 00:59
@renovate renovate bot force-pushed the renovate/webpack-cli-5.x branch 6 times, most recently from feffd30 to 74e5198 Compare October 28, 2023 04:42
@renovate renovate bot force-pushed the renovate/webpack-cli-5.x branch from db44940 to 0e66fd5 Compare March 16, 2024 00:19
@renovate renovate bot force-pushed the renovate/webpack-cli-5.x branch from 0e66fd5 to 1c19c91 Compare March 23, 2024 15:33
@renovate renovate bot force-pushed the renovate/webpack-cli-5.x branch from 1c19c91 to fcc59c0 Compare March 28, 2024 03:28
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
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
0 participants