Update webpack-merge to version 1.1.1 🚀

[greenkeeperio-bot]

Hello lovely humans,

webpack-merge just published its new version 1.1.1.

State	Update 🚀
Dependency	webpack-merge
New version	1.1.1
Type	devDependency

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 ✨

You rock!

🌴

---

The new version differs by 14 commits .

• 9b0d91c 1.1.1
• 2d76496 Update lib
• abfa23c fix(merge) - Support merge([<config>]) format officially
• a86bdd5 1.1.0
• 9524e7a Update lib
• 55ab699 feat(merge) - Allow merge array and object merging to be customized
• 162cae0 1.0.2
• ca605a4 Update lib
• fd39e5a fix(merge) - Merge should not mutate inputs with mismatches keys
• 0a8bffe Add @steven-haddix to contributors
• 7a6a62c Merge pull request #42 from steven-haddix/new-object-doc-update
• 26dba34 Updated README to explain merge produces new objects not references
• 62ba2ec readme - Add missing .
• 6f0e3cd readme - Drop extra =

See the full diff.

---

This pull request was created by greenkeeper.io.

_{Tired of seeing this sponsor message? ⚡ greenkeeper upgrade}