fix(gatsby-plugin-netlify-cms): Fix minimizer for production builds with gatsby-plugins-netlify-cms #14783
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
freiksenet
changed the title
freiksenet
approved these changes
Jun 14, 2019
freiksenet
added
the
bot: merge on green
|
this PR breaks my It will cause |
mxxk
pushed a commit
to mxxk/gatsby
that referenced
this pull request
Jun 21, 2019
…ith gatsby-plugins-netlify-cms (gatsbyjs#14783)
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.
Description
When building for production with gatsby-plugin-netlify-cms, node hangs at 'Building production JavaScript and CSS bundles', eventually throwing an out of memory error.
I found out that the problem is with Webpack 'minimize'.
Using the minimizer setting from the original Webpack configuration of Gatsby fixes the issue.
Related Issues
Possibly related to and fixes #14418