search

wopian / hibari

🦊 Vue app for Kitsu
https://hibari.moe
MIT License
26 stars 9 forks source link

build: update devdependency webpack-merge to ~5.4.0 #646

Closed renovate[bot] closed 3 years ago

renovate[bot] commented 4 years ago

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
webpack-merge ~4.2.0 -> ~5.4.0 age adoption passing confidence

Release Notes

survivejs/webpack-merge ### [`v5.4.0`](https://togithub.com/survivejs/webpack-merge/blob/master/CHANGELOG.md#​540--2020-10-30) [Compare Source](https://togithub.com/survivejs/webpack-merge/compare/v5.3.0...v5.4.0) - Fix - Fall back correctly in `mergeWithRules` for cases that aren't matched. [#​157](https://togithub.com/survivejs/webpack-merge/issues/157) [#​158](https://togithub.com/survivejs/webpack-merge/issues/158) - Fix - Don't throw if using `mergeWithRules` without a rule [#​151](https://togithub.com/survivejs/webpack-merge/issues/151) - Feat - Throw if `undefined` is passed to `merge` as a structure to merge ### [`v5.3.0`](https://togithub.com/survivejs/webpack-merge/blob/master/CHANGELOG.md#​530--2020-10-30) [Compare Source](https://togithub.com/survivejs/webpack-merge/compare/v5.2.0...v5.3.0) - Fix - Expose `Configuration` type through a generic to TypeScript to support both webpack 4 and 5 [#​141](https://togithub.com/survivejs/webpack-merge/issues/141) [#​154](https://togithub.com/survivejs/webpack-merge/issues/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`](https://togithub.com/survivejs/webpack-merge/blob/master/CHANGELOG.md#​520--2020-10-07) [Compare Source](https://togithub.com/survivejs/webpack-merge/compare/v5.1.4...v5.2.0) - Feature - Support advanced merging cases through `mergeWithRules` [#​146](https://togithub.com/survivejs/webpack-merge/issues/146) [#​149](https://togithub.com/survivejs/webpack-merge/issues/149) ### [`v5.1.4`](https://togithub.com/survivejs/webpack-merge/blob/master/CHANGELOG.md#​514--2020-09-09) [Compare Source](https://togithub.com/survivejs/webpack-merge/compare/v5.1.3...v5.1.4) - Fix - Expose `CustomizeRule` for TypeScript users [#​147](https://togithub.com/survivejs/webpack-merge/issues/147) ### [`v5.1.3`](https://togithub.com/survivejs/webpack-merge/blob/master/CHANGELOG.md#​513--2020-08-30) [Compare Source](https://togithub.com/survivejs/webpack-merge/compare/v5.1.2...v5.1.3) - Fix - Allow merging a `RegExp` to itself [#​145](https://togithub.com/survivejs/webpack-merge/issues/145) ### [`v5.1.2`](https://togithub.com/survivejs/webpack-merge/blob/master/CHANGELOG.md#​512--2020-08-18) [Compare Source](https://togithub.com/survivejs/webpack-merge/compare/v5.1.1...v5.1.2) - Fix - Allow overriding an object field with `null` [#​144](https://togithub.com/survivejs/webpack-merge/issues/144) ### [`v5.1.1`](https://togithub.com/survivejs/webpack-merge/blob/master/CHANGELOG.md#​511--2020-08-04) [Compare Source](https://togithub.com/survivejs/webpack-merge/compare/v5.1.0...v5.1.1) - Fix - Drop `` from **index.d.ts** [#​143](https://togithub.com/survivejs/webpack-merge/issues/143) ### [`v5.1.0`](https://togithub.com/survivejs/webpack-merge/blob/master/CHANGELOG.md#​510--2020-08-03) [Compare Source](https://togithub.com/survivejs/webpack-merge/compare/v5.0.9...v5.1.0) - 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`](https://togithub.com/survivejs/webpack-merge/blob/master/CHANGELOG.md#​509--2020-07-09) [Compare Source](https://togithub.com/survivejs/webpack-merge/compare/v5.0.8...v5.0.9) - Fix - Don't crash on `merge()` and `merge([])`. Now `{}` is returned in these corner cases. ### [`v5.0.8`](https://togithub.com/survivejs/webpack-merge/blob/master/CHANGELOG.md#​508--2020-07-07) [Compare Source](https://togithub.com/survivejs/webpack-merge/compare/v5.0.7...v5.0.8) - Fix - Support Node 10 [#​138](https://togithub.com/survivejs/webpack-merge/issues/138) ### [`v5.0.7`](https://togithub.com/survivejs/webpack-merge/blob/master/CHANGELOG.md#​507--2020-07-06) [Compare Source](https://togithub.com/survivejs/webpack-merge/compare/v5.0.6...v5.0.7) - Fix - Drop tslib dependency by setting `"importHelpers": false,` ### [`v5.0.6`](https://togithub.com/survivejs/webpack-merge/blob/master/CHANGELOG.md#​506--2020-07-06) [Compare Source](https://togithub.com/survivejs/webpack-merge/compare/v5.0.5...v5.0.6) - Fix - Add tslib to dependencies ### [`v5.0.5`](https://togithub.com/survivejs/webpack-merge/blob/master/CHANGELOG.md#​505--2020-07-06) [Compare Source](https://togithub.com/survivejs/webpack-merge/compare/v5.0.4...v5.0.5) - Tech - Optimize build size (UMD isn't needed) ### [`v5.0.4`](https://togithub.com/survivejs/webpack-merge/blob/master/CHANGELOG.md#​504--2020-07-06) [Compare Source](https://togithub.com/survivejs/webpack-merge/compare/v5.0.3...v5.0.4) - Documentation - Use CommonJS imports at the examples. [#​137](https://togithub.com/survivejs/webpack-merge/issues/137) ### [`v5.0.3`](https://togithub.com/survivejs/webpack-merge/blob/master/CHANGELOG.md#​503--2020-07-06) [Compare Source](https://togithub.com/survivejs/webpack-merge/compare/v5.0.0...v5.0.3) - Feature - Support TypeScript out of the box. [#​84](https://togithub.com/survivejs/webpack-merge/issues/84) [#​86](https://togithub.com/survivejs/webpack-merge/issues/86) [#​95](https://togithub.com/survivejs/webpack-merge/issues/95) [#​110](https://togithub.com/survivejs/webpack-merge/issues/110) [#​112](https://togithub.com/survivejs/webpack-merge/issues/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](https://togithub.com/survivejs/webpack-merge/issues/45) [#​99](https://togithub.com/survivejs/webpack-merge/issues/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](https://togithub.com/survivejs/webpack-merge/issues/81) - Fix - Drop lodash in favor of simpler dependencies. [#​134](https://togithub.com/survivejs/webpack-merge/issues/134) - Fix - Make `unique` merge from right to left to match behavior elsewhere. [#​119](https://togithub.com/survivejs/webpack-merge/issues/119) - Fix - Make sure `unique` doesn't lose non-unique items to merge. [#​125](https://togithub.com/survivejs/webpack-merge/issues/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`](https://togithub.com/survivejs/webpack-merge/compare/v4.2.2...v5.0.0) [Compare Source](https://togithub.com/survivejs/webpack-merge/compare/v4.2.2...v5.0.0)

Renovate configuration

:date: Schedule: "before 9am,after 5pm" in timezone Europe/London.

:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.

:recycle: Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

:no_bell: Ignore: Close this PR and you won't be reminded about this update again.

This PR has been generated by WhiteSource Renovate. View repository job log here.

renovate[bot] commented 3 years ago

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.