[WIP] Use Webpack 5 and add cache option#13348
Closed
filipesilva wants to merge 2 commits into
Closed
Conversation
Add an option to enable Webpacks persistent cache (webpack/webpack#8162).
alan-agius4
reviewed
Jan 2, 2019
| "type": "boolean", | ||
| "description": "Output profile events for Chrome profiler.", | ||
| "default": false | ||
| }, |
Collaborator
There was a problem hiding this comment.
Note: let’s remember to add these in the CLI schema
|
Hi @filipesilva! This PR has merge conflicts due to recent upstream merges. |
Collaborator
|
Closing since this was a POC |
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
Extremely experimental. Just opening a PR to run the Webpack 5 alphas through the test suite and see what breaks.
We will only update to Webpack 5 once it is stable and most of the plugins we use also support it.