Skip to content

chore(deps): update dependency webpack-merge to v5 #2583

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

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 21, 2020

This PR contains the following updates:

Package Type Update Change
webpack-merge devDependencies major ^4.1.1 -> ^5.0.0

Release Notes

survivejs/webpack-merge

v5.0.9

Compare Source

  • Fix - Don't crash on merge() and merge([]). Now {} is returned in these corner cases.

v5.0.8

Compare Source

v5.0.7

Compare Source

  • Fix - Drop tslib dependency by setting "importHelpers": false,

v5.0.6

Compare Source

  • Fix - Add tslib to dependencies

v5.0.5

Compare Source

  • Tech - Optimize build size (UMD isn't needed)

v5.0.4

Compare Source

  • Documentation - Use CommonJS imports at the examples. #​137

v5.0.3

Compare Source

  • Feature - Support TypeScript out of the box. #​84 #​86 #​95 #​110 #​112
  • Deprecation - merge.smart has been dropped as it's tricky to support all the corner cases. Instead, it's better to use the provided utilities to put together a merge that fits your case.
  • Deprecation - mergeStrategy has been dropped in favor of using mergeWithCustomize with customizeArray and customizeObject.
  • Deprecation - merge.multiple has been dropped as the functionality was too specific and it's better to implement in the user space if needed.
  • Breaking - merge has been moved as a regular import (i.e. import { merge } from 'webpack-merge').
  • Breaking - Merge customization has been moved behind mergeWithCustomize.
  • Breaking - Bump supported Node version to 12
  • Feature - customizeArray supports wildcards now. Example: 'entry.*': 'prepend'. #​45 #​99
  • Feature - Throw an error in case a Promise is being merged. It's better to wrap configuration within a Promise and merge inside it. #​81
  • Fix - Drop lodash in favor of simpler dependencies. #​134
  • Fix - Make unique merge from right to left to match behavior elsewhere. #​119
  • Fix - Make sure unique doesn't lose non-unique items to merge. #​125

Special thanks to Google and Addy Osmani for supporting the work financially as it allowed me to complete the work required by the new major release.

v5.0.0

Compare Source


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

renovate bot commented Jul 21, 2020

Renovate Ignore Notification

As this PR has been closed unmerged, Renovate will ignore this upgrade and you will not receive PRs for any future 5.x releases. However, if you upgrade to 5.x manually then Renovate will then reenable updates for minor and patch updates automatically.

If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.

@renovate renovate bot deleted the renovate/webpack-merge-5.x branch July 21, 2020 03:17
@github-actions
Copy link

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 22, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants