Skip to content

build: update webpack-merge to version 5.1.2#18174

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

build: update webpack-merge to version 5.1.2#18174
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/webpack-merge-5.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Jul 7, 2020

This PR contains the following updates:

Package Type Update Change
webpack-merge dependencies major 4.2.2 -> 5.1.2
webpack-merge devDependencies major 4.2.2 -> 5.1.2

Release Notes

survivejs/webpack-merge

v5.1.2

Compare Source

  • Fix - Allow overriding an object field with null #​144

v5.1.1

Compare Source

  • Fix - Drop <reference types="webpack-dev-server" /> from index.d.ts #​143

v5.1.0

Compare Source

  • Feature - Expose merge as default for backwards-compatibility with TypeScript. Now import merge from "webpack-merge"; works there. In CommonJS, the default alias is exposed through default property due to technical constraints.

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: "after 10pm every weekday,before 4am every weekday,every weekend" in timezone America/Tijuana.

🚦 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 these updates 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 added action: merge The PR is ready for merge by the caretaker target: major This PR is targeted for the next major release labels Jul 7, 2020
alan-agius4
alan-agius4 previously approved these changes Jul 7, 2020
@alan-agius4 alan-agius4 removed the action: merge The PR is ready for merge by the caretaker label Jul 7, 2020
@alan-agius4 alan-agius4 dismissed their stale review July 7, 2020 09:11

Need to address the breaking change

@renovate renovate Bot changed the title build: update webpack-merge to version 5.0.8 build: update webpack-merge to version 5.0.9 Jul 9, 2020
@renovate renovate Bot force-pushed the renovate/webpack-merge-5.x branch from 8a46c42 to f91b3c8 Compare July 9, 2020 12:23
@renovate renovate Bot force-pushed the renovate/webpack-merge-5.x branch from f91b3c8 to 698209d Compare July 25, 2020 14:37
@renovate renovate Bot changed the title build: update webpack-merge to version 5.0.9 build: update webpack-merge to version 5.1.0 Aug 3, 2020
@renovate renovate Bot force-pushed the renovate/webpack-merge-5.x branch from 698209d to ad1fed8 Compare August 3, 2020 06:40
@renovate renovate Bot changed the title build: update webpack-merge to version 5.1.0 build: update webpack-merge to version 5.1.1 Aug 4, 2020
@renovate renovate Bot force-pushed the renovate/webpack-merge-5.x branch from ad1fed8 to d0d7b27 Compare August 4, 2020 07:17
@renovate renovate Bot force-pushed the renovate/webpack-merge-5.x branch from d0d7b27 to 20a2798 Compare August 18, 2020 16:48
@renovate renovate Bot changed the title build: update webpack-merge to version 5.1.1 build: update webpack-merge to version 5.1.2 Aug 18, 2020
@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented Aug 27, 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 August 27, 2020 08:04
@angular-automatic-lock-bot
Copy link
Copy Markdown

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot Bot locked and limited conversation to collaborators Sep 27, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

target: major This PR is targeted for the next major release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants