An in-range update of webpack is breaking the build 🚨

[greenkeeper]

Version 2.3.0 of webpack just got published.

Branch	Build failing 🚨
Dependency	webpack
Current Version	2.2.1
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As webpack is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

---

Status Details

• ❌ continuous-integration/travis-ci/pr The Travis CI build could not complete due to an error Details

Release Notes

v2.3.0

Features:

• add extensions option to DllReferencePlugin
• add warningsFilter to UglifyJsPlugin to hide warnings selectively
• add extractComments to UglifyJsPlugin to move kept comments into separate file (i. e. LICENSE file)
• validate relative and absolute paths in configuration
• validate stats options
• allow to match on compiler (name in configuration) in rules
  • i. e. allows to specify different rules for extract-text-webpack-plugin or html-webpack-plugin
• Allow to pass multiple entries via CLI
• Performance improvements
• CommonsChunkPlugin give errors on incorrect options
• add module.strictExportPresence to make missing export an error instead of warning
• Compiler emits watch-close event when the watcher is closed
• Allow additional compress options in UglifyJsPlugin
• empty chunk numbers are not flags in every chunk, this improves caching invalidation

Bugfixes:

• OccurrenceOrderPlugin now counts occurrences correctly
• Fix cheap-source-maps when combined with ES Modules (lines were offset)
• Watcher now detects file deleting correctly
• Resolve output path if relative output path is given via CLI
• Handle stack traces in errors correctly
• Some usages of System now generate valid code i. e. System.global
• Dynamic property names are now parsed and can contain webpack stuff (i. e. imports)
• Empty enviroment variables are now supported in the EnvironmentPlugin
• (Maybe) Fixes chunk loading in IE when script is cached

Commits

The new version differs by 487 commits .

• 46dc08e 2.3.0
• 01c06de Merge pull request #4527 from webpack/bugfix/issue-4472
• 23e1f7c install Promise early in chunk cache
• 0c137cb Merge pull request #4521 from chicoxyzzy/patch-1
• 98ea823 Merge pull request #4503 from eirikurn/empty-env-variables
• 0058a2e Use ts-loader instead of deprecated typescript-loader
• 3e787ea Merge pull request #4502 from webpack/TheLarkInn-patch-1
• 335ce5f Merge pull request #4471 from SteveMieskoski/increase-coverage-for-AutomaticPrefetchPlugin
• fadafb2 Merge pull request #4504 from timse/do-not-merge-empty-chunks
• a9972a3 Merge pull request #4505 from rouzbeh84/hotfix/hotlinking-examples-index
• a5272e8 hotlink examples in readme
• d67e125 fix up tests
• d7ae9ad do not incorporate chunks without modules
• 003cef9 EnvironmentPlugin: Support empty env variables
• 7db849d Update README.md

There are 250 commits in total. See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴