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 webpack-cli to v4 #139

Merged
merged 4 commits into from
Apr 8, 2021
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 24, 2021

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
webpack-cli 3.3.12 -> 4.6.0 age adoption passing confidence

Release Notes

webpack/webpack-cli

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

@renovate renovate bot force-pushed the renovate/webpack-cli-4.x branch 4 times, most recently from 47c9256 to b29b0d0 Compare April 8, 2021 06:56
@renovate renovate bot force-pushed the renovate/webpack-cli-4.x branch from b29b0d0 to 31a063e Compare April 8, 2021 07:51
@renovate renovate bot force-pushed the renovate/webpack-cli-4.x branch from 31a063e to 0737027 Compare April 8, 2021 08:02
@foxundermoon foxundermoon merged commit f2aae53 into master Apr 8, 2021
@foxundermoon foxundermoon deleted the renovate/webpack-cli-4.x branch April 8, 2021 08:08
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.

None yet

2 participants