This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of webpack-merge.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
With Integrationsfirst-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.
Screencast Try it today. Free for private repositories during beta.
Hello lovely humans,
webpack-merge just published its new version 2.6.1.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of webpack-merge. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
The new version differs by 159 commits .
bf05fae
2.6.1
725b1c4
Update lib
814a219
fix -
merge.smart
should not merge rules that have differingenforce
fields362278f
2.6.0
964a779
Update lib
9e7fd59
fix - Support
replace
mode formerge.smartStrategy
cf7a35e
2.5.0
22ab1a1
Update lib
9758818
fix - Make sure
merge.smartStrategy
works with higher level nestingb228b1f
chore - Clean up readme headers
87d33d9
2.4.0
9c3ccbb
Update lib
7b50e2b
fix(unique) - Drop
includes
c0f3b73
Update changelog
13d3647
Add
merge.unique
helperThere are 159 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.