fix: reset HTMLEntrypoint state after build (fix #1211) #1214
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'm not sure if this is "the right solution", but it did seem the most obvious one to me as an outsider, and it does appear to work (fixes #1211). I don't love that it exposes a method (
HTMLEntrypoint::initialize
) that should probably be private somehow (e.g. calling it after construction but before being "done" may lead to weird/inconsistent states), but I needed a way for the Webpack plugin to reset the HTMLEntrypoint to its pristine/initial state so that it could be reused for subsequent calls tobuild
that used the cachedwebpack
instance (and perhaps a stern warning in a doc comment would be sufficient here...). Open to feedback / alternatives, of course, just wanted to help get this unblocked.@krisselden I think you made the original PR that refactored the file output to a Webpack plugin. Do you have thoughts on this?