Jeff Posnick

That code is in https://github.com/GoogleChromeLabs/preload-webpack-plugin/tree/v3

I'm not familiar with that option in `html-webpack-plugin`. What would the syntax for the placeholder/injection point ``s look like in the scenario you describe?

CC: @housseindjirdeh, as this is a fundamental question about the future of this plugin.

That's fun 😄 We can add in `html-webpack-plugin` v4 compatibility as part of the `v3.0.0-beta` releases, and then hopefully move that to be a final `v3.0.0` release in the near...

Sorry for the lack of updates—I've been trying to get things upgraded for `html-webpack-plugin` v4 (in the same branch that added support for webpack v4), and run into a couple...

Hey all—could folks give `npm install [email protected]` a try? That is meant to add support for `html-webpack-plugin` v4, but I did have to remove a some features in the process...

Thanks—I'm still working out some of the ergonomics with `html-webpack-plugin` v4 (see https://github.com/jantimon/html-webpack-plugin/issues/1091#issuecomment-434708455), but that at least gives folks who are on the bleeding edge something to work with 😄

So both https://github.com/jantimon/html-webpack-plugin/issues/1091 and https://github.com/jantimon/html-webpack-plugin/issues/1092 remain open, with the first issue being more serious with regards to how this plugin integrates with `html-webpack-plugin` v4. `npm install [email protected]` should give folks...

See also https://github.com/GoogleChrome/samples/pull/209 where I'm making a similar update.

Sure; that seems like a worthwhile effort. I'll add it to my plate.