Closed psharma-ii closed 1 year ago
Hi!
Please create a minimal reproduction so that we can look into it. Also please note that in 5.3 we made this error message more meaningful: https://www.gatsbyjs.com/docs/reference/release-notes/v5.3/#improved-error-messages
So if you can upgrade to Gatsby 5 I'd recommend doing that.
Hiya!
This issue has gone quiet. Spooky quiet. 👻
We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 20 days since the last update here. If we missed this issue or if you want to keep it open, please reply here. As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!
Thanks for being a part of the Gatsby community! 💪💜
Hi!
Since we didn't receive an answer for 7 days or more about the ask of a reproduction I'm going to close this now, as we can't do much to help without a reproduction. If you are able to create a minimal reproduction for this then please do answer here or open a new issue with a reproduction. Thanks!
Preliminary Checks
Description
We are running into an issue about webpack and not getting any specific details about what is failing.
Error looks like
Full Build Log
gatsby info
Reproduction Link
NA
Steps to Reproduce
1.Have the above configuration
Expected Result
Build should be successful
Actual Result
Build fails with the following error
Environment
Config Flags
GATSBY_CPU_COUNT=2 NODE_OPTIONS=--max-old-space-size=16384