Skip to content

chore(deps): update dependency webpack-cli to v6 #387

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
Open
wants to merge 1 commit into
base: develop
Choose a base branch
from
Open

chore(deps): update dependency webpack-cli to v6 #387

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 22, 2024 •
edited
Loading

This PR contains the following updates:

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

Release Notes

webpack/webpack-cli (webpack-cli)

v6.0.1

Compare Source

Bug Fixes

v6.0.0

Compare Source

BREAKING CHANGES
  • the minimum required Node.js version is 18.12.0
  • removed init, loader and plugin commands in favor create-webpack-app
  • dropped support for webpack-dev-server@v4
  • minimum supported webpack version is 5.82.0
Bug Fixes
Features

5.1.4 (2023-06-07)

Bug Fixes
  • multi compiler progress output (f659624)

5.1.3 (2023-06-04)

Bug Fixes

5.1.2 (2023-06-04)

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)

5.1.1 (2023-05-09)

Bug Fixes

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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Dec 22, 2024
@renovate Renovate
Copy link
Contributor Author

renovate bot commented Dec 22, 2024 •
edited
Loading

⚠️ 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 v16.20.2. 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.82.0" from [email protected]
npm error node_modules/webpack-cli
npm error   dev webpack-cli@"6.0.1" 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-11T11_37_35_210Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2025-02-11T11_37_35_210Z-debug-0.log

@renovate renovate bot force-pushed the renovate/webpack-cli-6.x branch from 22c8428 to 312ddc6 Compare February 11, 2025 11:37
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 Pull requests that update a dependency file
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants