Closed greenkeeper[bot] closed 5 years ago
Update to this version instead 🚀
The 2.2.0 release includes adds support for include: 'initial'
. Thanks to @yyx990803 for the contribution!
Update to this version instead 🚀
The new version differs by 17 commits.
f604879
2.3.0
0f80892
Merge pull request #36 from laysent/master
40a1220
Merge branch 'master' into master
aca5288
rename option names
99b7f3c
merge from upstream
de90ae6
Merge pull request #1 from alechill/master
374ad6f
Fixed all-assets being treated as a real chunk in doesChunkBelongToHTML - it should not be attempted to filtered as if it were a chunk, they are just files to be black/whitelisted in config
e29cdd4
Merge pull request #54 from toxic-johann/master
cf895ed
[update] add excludeHtmlNames to solve problem mentioned in #48
4ff53e0
Merge branch 'master' of https://github.com/GoogleChromeLabs/preload-webpack-plugin
748dbfa
update README to point out potential issue
11da208
Merge branch 'master' into master
e19777f
Merge pull request #1 from GoogleChromeLabs/master
cdb459e
Merge remote-tracking branch 'refs/remotes/GoogleChrome/master'
487f77a
add fileWhitelist
to include specific files
There are 17 commits in total.
See the full diff
Version 2.1.0 of preload-webpack-plugin was just published.
The version 2.1.0 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 preload-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
2.1.0What's new?
The 2.1.0 release contains a bug fix that ensures proper functionality when there are multiple
HtmlWebpackPlugin
modules in your webpack build process.Thanks to @toxic-johann for the contribution!
Notable PRs
Commits
The new version differs by 6 commits.
c88ba96
Merge pull request #37 from toxic-johann/master
388001e
Merge pull request #41 from GoogleChromeLabs/gauntface-patch-1
88da76d
Merge pull request #42 from GoogleChromeLabs/gauntface-patch-2
c16373f
Update README.md
34ed355
Update package.json
5d8a9ed
[fix] fix duplicate outputs when using with multiple instances of HtmlWebpackPlugin GoogleChrome#27
See the full diff
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper bot :palm_tree: