• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Features

• When using functions as plugins they are now also called with the compiler as parameter
  • This make it possible to use arrow functions as plugins
• splitChunks.maxSize now emits a warning when minSize > maxSize
• Loaders have now access to a getResolve method to create their own resolver function with custom options

Bugfixes

• splitChunks.cacheGroups.xxx.enforce now behaves as documented and enforce chunk creation
• splitChunks.cacheGroups.xxx.enforce now no longer deletes minSize for maxSize
• fixes a bug where splitChunks cause cacheGroups to be incorrectly merged when using the same name
  • now conditions are considered per cacheGroup
  • the correct cache group comment is displayed in stats
• fixes a bug which causes providedExports not to be updated on rebuilds when using export * from

The new version differs by 12 commits.

• f47bf8b 4.27.0
• a67ffcd Merge pull request #8452 from webpack/feature/resolveWithOptions
• 96f625c Merge pull request #8457 from webpack/bugfix/rebuild-provided-exports
• 56feccc convert test case to normal function for node.js 6 support
• 2f4296e fix a bug which causes incorrect providedExports for cached modules
• f944002 Merge pull request #8451 from webpack/bugfix/split-chunks
• 162da1c add getResolve method to loader context
• 3b46b48 enforce doesn't affect minSize for maxSize
• 72a8a1f Merge pull request #8440 from Connormiha/oprimize-chunk-can-be-integrated
• 537d3e4 Cache hasRunstime in chunk
• e3e8a68 Merge pull request #8405 from xiaoxiaojx/fix-function-plugin-apply
• 70b9a1b fix parameter missing when plugin type is a funtion

See the full diff

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

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

• engines was only updated if it defined a single version, not a range.
• .nvmrc was updated to Node.js 10
• .travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖

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