1 | # Changelog
|
2 |
|
3 | ## 5.7.3 / 2020-12-22
|
4 |
|
5 | - Fix - Don't merge strings with objects in `mergeWithRules`. #172
|
6 |
|
7 | ## 5.7.2 / 2020-12-16
|
8 |
|
9 | - Fix - If there's no match when using `merge` operation with `mergeWithRules`, use default merge behavior as a fallback. #167
|
10 |
|
11 | ## 5.7.1 / 2020-12-16
|
12 |
|
13 | - Fix - Fix a merge failure for `mergeWithRules` when non-array matches are merged. #166
|
14 |
|
15 | ## 5.7.0 / 2020-12-12
|
16 |
|
17 | - Feat - Throw a `TypeError` if trying to use `mergeWithRules` with invalid configuration types for `append`/`prepend`/`merge` operations.
|
18 |
|
19 | ## 5.6.1 / 2020-12-11
|
20 |
|
21 | - Fix - Drop extraneous logging.
|
22 |
|
23 | ## 5.6.0 / 2020-12-11
|
24 |
|
25 | - Feat - Support `merge` (`CustomizeRule.Merge`) for objects at `mergeWithRules`. This is useful for merging loader options for example. #163
|
26 |
|
27 | ## 5.5.0 / 2020-12-10
|
28 |
|
29 | - Feat - Allow `mergeWithRules` to merge based on rules without a match. #151 #159
|
30 |
|
31 | ## 5.4.1 / 2020-12-08
|
32 |
|
33 | - Fix - Allow `mergeUnique` to work with arbitrary order. #161
|
34 |
|
35 | ## 5.4.0 / 2020-10-30
|
36 |
|
37 | - Fix - Fall back correctly in `mergeWithRules` for cases that aren't matched. #157 #158
|
38 | - Fix - Don't throw if using `mergeWithRules` without a rule #151
|
39 | - Feat - Throw if `undefined` is passed to `merge` as a structure to merge
|
40 |
|
41 | ## 5.3.0 / 2020-10-30
|
42 |
|
43 | - Fix - Expose `Configuration` type through a generic to TypeScript to support both webpack 4 and 5 #141 #154
|
44 |
|
45 | In case you use webpack 4, please change your typing as instructed in the readme as the default type is loose but non-breaking.
|
46 |
|
47 | ## 5.2.0 / 2020-10-07
|
48 |
|
49 | - Feature - Support advanced merging cases through `mergeWithRules` #146 #149
|
50 |
|
51 | ## 5.1.4 / 2020-09-09
|
52 |
|
53 | - Fix - Expose `CustomizeRule` for TypeScript users #147
|
54 |
|
55 | ## 5.1.3 / 2020-08-30
|
56 |
|
57 | - Fix - Allow merging a `RegExp` to itself #145
|
58 |
|
59 | ## 5.1.2 / 2020-08-18
|
60 |
|
61 | - Fix - Allow overriding an object field with `null` #144
|
62 |
|
63 | ## 5.1.1 / 2020-08-04
|
64 |
|
65 | - Fix - Drop `<reference types="webpack-dev-server" />` from **index.d.ts** #143
|
66 |
|
67 | ## 5.1.0 / 2020-08-03
|
68 |
|
69 | - 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.
|
70 |
|
71 | ## 5.0.9 / 2020-07-09
|
72 |
|
73 | - Fix - Don't crash on `merge()` and `merge([])`. Now `{}` is returned in these corner cases.
|
74 |
|
75 | ## 5.0.8 / 2020-07-07
|
76 |
|
77 | - Fix - Support Node 10 #138
|
78 |
|
79 | ## 5.0.7 / 2020-07-06
|
80 |
|
81 | - Fix - Drop tslib dependency by setting `"importHelpers": false,`
|
82 |
|
83 | ## 5.0.6 / 2020-07-06
|
84 |
|
85 | - Fix - Add tslib to dependencies
|
86 |
|
87 | ## 5.0.5 / 2020-07-06
|
88 |
|
89 | - Tech - Optimize build size (UMD isn't needed)
|
90 |
|
91 | ## 5.0.4 / 2020-07-06
|
92 |
|
93 | - Documentation - Use CommonJS imports at the examples. #137
|
94 |
|
95 | ## 5.0.3 / 2020-07-06
|
96 |
|
97 | - Feature - Support TypeScript out of the box. #84 #86 #95 #110 #112
|
98 | - 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.
|
99 | - Deprecation - `mergeStrategy` has been dropped in favor of using `mergeWithCustomize` with `customizeArray` and `customizeObject`.
|
100 | - Deprecation - `merge.multiple` has been dropped as the functionality was too specific and it's better to implement in the user space if needed.
|
101 | - Breaking - `merge` has been moved as a regular import (i.e. `import { merge } from 'webpack-merge'`).
|
102 | - Breaking - Merge customization has been moved behind `mergeWithCustomize`.
|
103 | - Breaking - Bump supported Node version to 12
|
104 | - Feature - `customizeArray` supports wildcards now. Example: `'entry.*': 'prepend'`. #45 #99
|
105 | - 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
|
106 | - Fix - Drop lodash in favor of simpler dependencies. #134
|
107 | - Fix - Make `unique` merge from right to left to match behavior elsewhere. #119
|
108 | - Fix - Make sure `unique` doesn't lose non-unique items to merge. #125
|
109 |
|
110 | 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.
|
111 |
|
112 | ## 4.2.2 / 2019-08-27
|
113 |
|
114 | - Fix - Update minimum version of lodash to 4.17.15 in order to avoid `npm audit warning`. #116
|
115 | - Docs - Improve `merge.unique` documentation. #103
|
116 | - Docs - Add clear note about precedence. #115
|
117 |
|
118 | ## 4.2.1 / 2019-01-04
|
119 |
|
120 | - Feature - Support `oneOf` at `merge.smart`. #111
|
121 | - Fix - If there's only single array to merge, clone it. #106
|
122 |
|
123 | ## 4.1.4 / 2018-08-01
|
124 |
|
125 | - Maintenance - Remove bitHound from the README as it closed down. #102
|
126 |
|
127 | ## 4.1.3 / 2018-06-14
|
128 |
|
129 | - Fix - Smart merge respects the existing loader order #79, #101
|
130 |
|
131 | ## 4.1.2 / 2017-02-22
|
132 |
|
133 | - Maintenance - Update lodash, #97, #98
|
134 |
|
135 | ## 4.1.1 / 2017-11-01
|
136 |
|
137 | - Docs - Add `customizeArray` and `customizeObject` examples. #93
|
138 |
|
139 | ## 4.1.0 / 2017-03-16
|
140 |
|
141 | - Feature - `merge.multiple` to allow working with webpack multi-compiler mode. It accepts multiple objects and returns an array you can push to webpack. #74
|
142 |
|
143 | ## 4.0.0 / 2017-03-06
|
144 |
|
145 | - Breaking feature - `merge.smart` allows re-ordering loaders like below. #70
|
146 |
|
147 | ```javascript
|
148 | merge.smart(
|
149 | {
|
150 | loaders: [
|
151 | {
|
152 | test: /\.js$/,
|
153 | loaders: ["babel"],
|
154 | },
|
155 | ],
|
156 | },
|
157 | {
|
158 | loaders: [
|
159 | {
|
160 | test: /\.js$/,
|
161 | loaders: ["react-hot", "babel"],
|
162 | },
|
163 | ],
|
164 | }
|
165 | );
|
166 | // will become
|
167 | {
|
168 | loaders: [
|
169 | {
|
170 | test: /\.js$/,
|
171 | // order of second argument is respected
|
172 | loaders: ["react-hot", "babel"],
|
173 | },
|
174 | ];
|
175 | }
|
176 | ```
|
177 |
|
178 | ## 3.0.0 / 2017-02-19
|
179 |
|
180 | - Breaking fix - `merge.smart` should not merge a child missing `include`/`exclude` to a parent that has either. This is safer and more predictable behavior than the old one. #69
|
181 |
|
182 | ## 2.6.1 / 2017-01-29
|
183 |
|
184 | - Bug fix - `merge.smart` should not merge rules that have differing `enforce` fields. #65
|
185 |
|
186 | ## 2.6.0 / 2017-01-27
|
187 |
|
188 | - Bug fix - Support `replace` mode for `merge.smartStrategy`. #63
|
189 |
|
190 | ## 2.5.0 / 2017-01-26
|
191 |
|
192 | - Bug fix - Make sure `merge.smartStrategy` works with higher level nesting like `'module.rules.use': 'prepend'`. #64
|
193 |
|
194 | ## 2.4.0 / 2017-01-12
|
195 |
|
196 | - Feature - Add `merge.unique` helper that plugs into `customizeArray`. This allows you to force only one plugin of a type to the end result. #58
|
197 |
|
198 | ## 2.3.1 / 2017-01-06
|
199 |
|
200 | - Bug fix - Clear up `CopyWebpackPlugin` handling. #56
|
201 |
|
202 | ## 2.3.0 / 2017-01-06
|
203 |
|
204 | - Refactor - Depend only on `lodash` instead of individual packages as latter has been discontinued. #52
|
205 |
|
206 | ## 2.2.0 / 2017-01-05
|
207 |
|
208 | - Bug fix - Drop `merge.smartStrategy(rules, plugins)` as that caused other issues (prototype copying for complex cases). That needs a better approach. #55
|
209 |
|
210 | ## 2.1.1 / 2017-01-05
|
211 |
|
212 | - Bug fix - Avoid recursion at `merge.smart`. #53
|
213 |
|
214 | ## 2.1.0 / 2017-01-05
|
215 |
|
216 | - Feature - Allow `merge.smartStrategy` to merge plugin contents. API: `merge.smartStrategy(rules, plugins)`. #44. Example:
|
217 |
|
218 | ```javascript
|
219 | const output = merge.smartStrategy(
|
220 | {
|
221 | entry: 'prepend', // or 'replace'
|
222 | 'module.loaders': 'prepend'
|
223 | },
|
224 | ['LoaderOptionsPlugin']
|
225 | )(object1, object2, object3, ...);
|
226 | ```
|
227 |
|
228 | ## 2.0.0 / 2016-12-22
|
229 |
|
230 | - Breaking - Disallow overriding configuration with empty arrays/objects (#48). If you want to override, use `merge.strategy`. Example:
|
231 |
|
232 | ```javascript
|
233 | const a = {
|
234 | entry: ["foo"],
|
235 | };
|
236 | const b = {
|
237 | entry: [],
|
238 | };
|
239 |
|
240 | merge(a, b); // Yields a result, not b like before.
|
241 | ```
|
242 |
|
243 | ## 1.1.2 / 2016-12-18
|
244 |
|
245 | - Bug fix - `merge({ entry: {} })` should return the same result as input instead of a function.
|
246 |
|
247 | ## 1.1.1 / 2016-12-11
|
248 |
|
249 | - Bug fix - Support previously undocumented, yet used, `merge([<object>])` format. This works with all available functions. #46
|
250 |
|
251 | ## 1.1.0 / 2016-12-09
|
252 |
|
253 | - Feature - Allow `merge` behavior to be customized with overrides. Example:
|
254 |
|
255 | ```javascript
|
256 | var output = merge({
|
257 | customizeArray(a, b, key) { return [...a, ...b]; },
|
258 | customizeObject(a, b, key) { return mergeWith(a, b); }
|
259 | })(object1, object2, object3, ...);
|
260 | ```
|
261 |
|
262 | This allows you to guarantee array uniqueness and so on.
|
263 |
|
264 | ## 1.0.2 / 2016-11-29
|
265 |
|
266 | - Bug fix - `merge` should not mutate inputs with mismatched keys.
|
267 |
|
268 | ## 1.0.0 / 2016-11-28
|
269 |
|
270 | - Feature: Support merging Webpack 2 Rule.use. #38
|
271 | - Bug fix - Don't concat loaders if the first matching entry's include/exclude doesn't match. #39
|
272 |
|
273 | ## 0.20.0 / 2016-11-27
|
274 |
|
275 | - Feature: Add support for merging functions. This feature has been designed `postcss` in mind. It executes the functions, picks their results, and packs them again.
|
276 |
|
277 | ## 0.19.0 / 2016-11-26
|
278 |
|
279 | - Feature: Add support for 'replace' option at `merge.strategy`. It literally replaces the old field value with the newer one. #40
|
280 |
|
281 | ## 0.18.0 / 2016-11-24
|
282 |
|
283 | - Feature: Add support for recursive definitions at `merge.strategy`. Example:
|
284 |
|
285 | ```javascript
|
286 | var output = merge.strategy({
|
287 | entry: 'prepend',
|
288 | 'module.loaders': 'prepend'
|
289 | })(object1, object2, object3, ...);
|
290 | ```
|
291 |
|
292 | - Feature: Add `merge.smartStrategy`. This combines the ideas of `merge.smart` and `merge.strategy` into one. Example:
|
293 |
|
294 | ```javascript
|
295 | var output = merge.smartStrategy({
|
296 | entry: 'prepend',
|
297 | 'module.loaders': 'prepend'
|
298 | })(object1, object2, object3, ...);
|
299 | ```
|
300 |
|
301 | ## 0.17.0 / 2016-11-16
|
302 |
|
303 | - Feature: Add support for `merge.strategy`. Now you can customize merging behavior per root level configuration field. Example: `merge.strategy({ entry: 'prepend' })(object1, object2, object3, ...);`. #17
|
304 |
|
305 | ## 0.16.0 / 2016-11-14
|
306 |
|
307 | - Feature: Add support for webpack 2 at `merge.smart`. It should pick up `module.rules` as you might expect now. #35
|
308 |
|
309 | ## 0.15.0 / 2016-10-18
|
310 |
|
311 | - Breaking: Rework `merge.smart` so that it **appends** loaders instead of **prepending** them. This is the logical thing to do as it allows you to specify behavior better as you `merge`. #32
|
312 |
|
313 | ## 0.14.1 / 2016-07-25
|
314 |
|
315 | - Docs: Improve package description. #23.
|
316 | - Bug fix - Let `merge.smart` merge loaders based on their full name instead of first letter. Thanks to @choffmeister. #26.
|
317 |
|
318 | ## 0.14.0 / 2016-06-05
|
319 |
|
320 | - Feature: Allow `merge.smart` to merge `loaders` if `exclude` is the same. Thanks to @mshwery. #21.
|
321 |
|
322 | ## 0.13.0 / 2016-05-24
|
323 |
|
324 | - Bug fix: Allow `merge.smart` to merge configuration if `include` is defined. Thanks to @blackrabbit99. #20.
|
325 |
|
326 | ## 0.12.0 / 2016-04-19
|
327 |
|
328 | - Feature: Support `include/exclude` at `merge.smart` for `loader` definition too. Thanks to @Whoaa512. #16.
|
329 |
|
330 | ## 0.11.0 / 2016-04-18
|
331 |
|
332 | - Feature: Support `include/exclude` at `merge.smart` when its set only in a parent. #15.
|
333 |
|
334 | ## 0.10.0 / 2016-04-10
|
335 |
|
336 | - Feature: Support `include/exclude` at `merge.smart`. Thanks to @siready. #14.
|
337 |
|
338 | ## 0.9.0 / 2016-04-08
|
339 |
|
340 | - Feature: Allow existing objects/arrays to be emptied with an empty object/array later in merge. This overriding behavior is useful for example emptying your `entry` configuration.
|
341 |
|
342 | ## 0.8.4 / 2016-03-17
|
343 |
|
344 | - Bug fix: _webpack-merge_ should not mutate inputs. #12
|
345 |
|
346 | ## 0.8.3 / 2016-03-02
|
347 |
|
348 | - Bug fix: Drop `files` field from _package.json_ as it wasn't including the dist correctly.
|
349 |
|
350 | ## 0.8.0 / 2016-03-02
|
351 |
|
352 | - Breaking: Change merging behavior so that only loaders get prepended. The rest follow appending logic. This makes `entry` array merging behavior logical. Prepend makes sense only for loaders after all. #10
|
353 |
|
354 | ## 0.7.3 / 2016-01-11
|
355 |
|
356 | - Bug fix: Do not error when there are no matching loaders. Thanks @GreenGremlin!
|
357 |
|
358 | ## 0.7.2 / 2016-01-08
|
359 |
|
360 | - Regenerate tarball. The problem was that there were some old dependencies included. Closes #7.
|
361 |
|
362 | ## 0.7.1 / 2016-01-03
|
363 |
|
364 | - Improve performance by defaulting to `concat` and by dropping a redundant check. Thanks @davegomez!
|
365 |
|
366 | ## 0.7.0 / 2015-12-31
|
367 |
|
368 | - Bug fix: Arrays get merged within nested structures correctly now. Array items are prepended (reverse order compared to earlier). This is related to the change made in _0.6.0_. Incidentally this change affects normal merge as well.
|
369 | - Smart merge: If a loader contains either `include` or `exclude`, it will generate separate entries instead of merging. Without this the configuration might change in an unpredictable manner.
|
370 |
|
371 | ## 0.6.0 / 2015-12-30
|
372 |
|
373 | - Support `preLoaders` and `postLoaders`. Previously only `loaders` were supported.
|
374 | - Breaking: Change smart merging behavior for `loaders` field so that it prepends loaders instead of appending them. The benefit of this is that now it's possible to specialize loader setup in a predictable manner. For example you can have a linter set up at the root and expect it to become evaluated first always.
|
375 |
|
376 | ## 0.5.1 / 2015-12-26
|
377 |
|
378 | - Fix `merge` object/array case (missing `bind`). The behavior should be correct now.
|
379 |
|
380 | ## 0.5.0 / 2015-12-26
|
381 |
|
382 | - Breaking: Push smart merging behind `merge.smart`. Now `merge` behaves exactly as in _0.3.0_ series.
|
383 |
|
384 | ## 0.4.0 / 2015-12-23
|
385 |
|
386 | - Dropped changelog generator. It's better to write these by hand.
|
387 | - Breaking: Added smart merging (@GreenGremlin)
|
388 |
|
389 | ## 0.3.2 / 2015-11-23
|
390 |
|
391 | - Tweaked changelog generator process.
|
392 |
|
393 | ## 0.3.1 / 2015-11-23
|
394 |
|
395 | - Added changelog generator.
|
396 |
|
397 | ## 0.3.0 / 2015-11-13
|
398 |
|
399 | - Improved formatting
|
400 | - Allowed an arbitrary amount of objects to be merged
|
401 |
|
402 | ## 0.2.0 / 2015-08-30
|
403 |
|
404 | - Only require lodash modules used by the package (@montogeek)
|
405 | - Removed lodash.isarray dependency, use Array.isArray standard object
|
406 |
|
407 | ## 0.1.3 / 2015-08-10
|
408 |
|
409 | - Improved README example
|
410 |
|
411 | ## 0.1.2 / 2015-07-01
|
412 |
|
413 | - Simplified example
|
414 |
|
415 | ## 0.1.1 / 2015-06-26
|
416 |
|
417 | - Fixed travis link
|
418 |
|
419 | ## 0.1.0 / 2015-06-26
|
420 |
|
421 | - Initial implementation
|