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-merge to v5 - abandoned #206

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

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jul 6, 2020

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
webpack-merge 4.2.2 -> 5.8.0 age adoption passing confidence

Release Notes

survivejs/webpack-merge

v5.8.0

Compare Source

  • Docs - Update env example to be webpack 5 compatible. #​177, #​180
  • Feat - Support strings as rules for TypeScript, not just enums. #​179, #​185

v5.7.3

Compare Source

  • Fix - Don't merge strings with objects in mergeWithRules. #​172

v5.7.2

Compare Source

  • Fix - If there's no match when using merge operation with mergeWithRules, use default merge behavior as a fallback. #​167

v5.7.1

Compare Source

  • Fix - Fix a merge failure for mergeWithRules when non-array matches are merged. #​166

v5.7.0

Compare Source

  • Feat - Throw a TypeError if trying to use mergeWithRules with invalid configuration types for append/prepend/merge operations.

v5.6.1

Compare Source

  • Fix - Drop extraneous logging.

v5.6.0

Compare Source

  • Feat - Support merge (CustomizeRule.Merge) for objects at mergeWithRules. This is useful for merging loader options for example. #​163

v5.5.0

Compare Source

  • Feat - Allow mergeWithRules to merge based on rules without a match. #​151 #​159

v5.4.1

Compare Source

  • Fix - Allow mergeUnique to work with arbitrary order. #​161

v5.4.0

Compare Source

  • Fix - Fall back correctly in mergeWithRules for cases that aren't matched. #​157 #​158
  • Fix - Don't throw if using mergeWithRules without a rule #​151
  • Feat - Throw if undefined is passed to merge as a structure to merge

v5.3.0

Compare Source

  • Fix - Expose Configuration type through a generic to TypeScript to support both webpack 4 and 5 #​141 #​154

In case you use webpack 4, please change your typing as instructed in the readme as the default type is loose but non-breaking.

v5.2.0

Compare Source

  • Feature - Support advanced merging cases through mergeWithRules #​146 #​149

v5.1.4

Compare Source

  • Fix - Expose CustomizeRule for TypeScript users #​147

v5.1.3

Compare Source

  • Fix - Allow merging a RegExp to itself #​145

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


Configuration

📅 Schedule: Branch creation - "after 9pm every weekday,every weekend,before 11am every weekday" in timezone Asia/Tokyo, 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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/webpack-merge-5.x branch 5 times, most recently from 3631eab to 4704fd3 Compare July 9, 2020 12:20
@renovate renovate bot force-pushed the renovate/webpack-merge-5.x branch 2 times, most recently from 5aca917 to 45d1d93 Compare August 4, 2020 07:10
@renovate renovate bot force-pushed the renovate/webpack-merge-5.x branch from 45d1d93 to 810e0b9 Compare August 18, 2020 16:41
@renovate renovate bot force-pushed the renovate/webpack-merge-5.x branch from 810e0b9 to 3198bc1 Compare August 30, 2020 06:26
@renovate renovate bot force-pushed the renovate/webpack-merge-5.x branch from 3198bc1 to add1b74 Compare September 9, 2020 07:44
@renovate renovate bot force-pushed the renovate/webpack-merge-5.x branch from add1b74 to 8e8e3e9 Compare October 7, 2020 09:34
@renovate renovate bot force-pushed the renovate/webpack-merge-5.x branch from 8e8e3e9 to 1971874 Compare October 30, 2020 17:42
@renovate renovate bot force-pushed the renovate/webpack-merge-5.x branch from 1971874 to 71750cc Compare November 12, 2020 11:07
@renovate renovate bot force-pushed the renovate/webpack-merge-5.x branch 5 times, most recently from f7f47d5 to ae4f664 Compare December 12, 2020 11:40
@renovate renovate bot force-pushed the renovate/webpack-merge-5.x branch 2 times, most recently from a1587ee to a2ce6f5 Compare December 16, 2020 14:09
@renovate renovate bot force-pushed the renovate/webpack-merge-5.x branch from a2ce6f5 to b9da6e0 Compare January 7, 2021 08:59
@renovate renovate bot force-pushed the renovate/webpack-merge-5.x branch from b9da6e0 to 9ab2519 Compare June 7, 2021 09:06
@renovate
Copy link
Author

renovate bot commented Mar 24, 2023

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@renovate renovate bot changed the title Update dependency webpack-merge to v5 Update dependency webpack-merge to v5 - abandoned Jul 9, 2024
Copy link
Author

renovate bot commented Jul 9, 2024

Autoclosing Skipped

This PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant