Update this fork of the plugin - Resolved conflicts - #12
Conversation
update to the latest base
Add excludeHtmlNames to solve problem mentioned in GoogleChromeLabs#48
…ML - it should not be attempted to filtered as if it were a chunk, they are just files to be black/whitelisted in config
Fixed all-assets being treated as a real chunk in doesChunkBelongToHML
+ use pascal case: "all-assets" to "allAssets" + rename "all" to "allChunks"
Provide a way to include all assets (issue #35)
…or prefetches async chunks
Implement webpack 4 support
…gin-updates Update for html-webpack-plugin v4 API
Changes for the v3 release
add media option for responsive preloading
|
@housseindjirdeh is the current "owner of record" for One of the open questions was whether he would maintain it going forward or whether finding a new home with a different maintainer made the most sense. I see that this repo is in the I'll let you and Houssein discuss 😄 |
I thought this repo was from @sodatea, since he is the author from the last 2 releases 😄 |
haoqunjiang
left a comment
There was a problem hiding this comment.
Thanks for the help. But the tests are not runnable, so there's still much work to do.
The work on this PR has been paused for more than a year now.
Recently, I worked on a project where the whitelisting ability — which is present on the
GoogleChromeLabs/preload-webpack-plugin— would be really handy.For what I saw, the only thing that was stopping the merge on the other PR was merge conflicts. Since I wasn't able to solve them directly for @jeffposnick, I did a new fork and solved them myself.
Let me know your thoughts on this. 👌