Update copy-webpack-plugin to the latest version 🚀

[greenkeeper]

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 4.5.1 of copy-webpack-plugin was just published.

Dependency	copy-webpack-plugin
Current Version	4.4.2
Type	devDependency

The version 4.5.1 is not covered by your current version range.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

It might be worth looking into these changes and trying to get this project onto the latest version of copy-webpack-plugin.

If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.

---

Release Notes

v4.5.1

2018-03-09

Bug Fixes

• package: update cacache v10.0.1...10.0.4 (dependencies) (#238) (0b288f9)

Performance Improvements

• index: switch to md4 for content hashing (#239) (2be8191)

Commits

The new version differs by 8 commits.

• 63dc9f9 chore(release): 4.5.1
• 0b288f9 fix(package): update cacache v10.0.1...10.0.4 (dependencies) (#238)
• 2be8191 perf(index): switch to md4 for content hashing (#239)
• c097601 chore(release): 4.5.0
• 1861730 feat(processPattern): add support for {RegExp) matches (pattern.test) (#235)
• 832f139 chore(release): 4.4.3
• 522c2b5 chore(package): update loader-utils v0.2.15...1.1.0 (#152)
• 445d548 fix(index): tapable deprecation warnings (webpack >= v4.0.0) (#234)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper bot 🌴