Document compiler.run() needs compiler.close() #4775
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/webpack-docs/webpack-js-org/47MgYVz4tTbq182vBVgqbSpYPVxS |
|
related to my comment webpack/webpack#12345 |
|
not sure why. the CLA bot seems stuck
|
|
Thanks for your contribution. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The API doc is not very clear regarding the need to call compiler.close() after compiler.run() (only the changelog was).
It seems to me important because persistent cache won't be flushed otherwise.
Also important to show that the callback takes an error that may be thrown if persistent caching fails.
Preview link: https://webpack-js-org-git-fork-slorber-patch-3-webpack-docs.vercel.app/api/node/#run