You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would expect the command to run without a crash 😄
Actual result
It crashed with the following error:
$ gatsby develop
/home/foo/broken-gatsby-develop-command/node_modules/yoga-layout-prebuilt/yoga-layout/build/Release/nbind.js:53
throw ex;
^
Error: write EACCES
at process.target._send (internal/child_process.js:762:20)
at process.target.send (internal/child_process.js:634:19)
at action (/home//foo/broken-gatsby-develop-command/node_modules/gatsby-cli/lib/reporter/loggers/ipc/index.js:58:13)
at dispatch (/home//foo/broken-gatsby-develop-command/node_modules/gatsby-cli/lib/reporter/redux/index.js:54:5)
at dispatch (/home//foo/broken-gatsby-develop-command/node_modules/gatsby-cli/lib/reporter/redux/internal-actions.js:42:7)
at dispatch (/home//foo/broken-gatsby-develop-command/node_modules/gatsby-cli/lib/reporter/redux/index.js:33:5)
at action.forEach.item (/home//foo/broken-gatsby-develop-command/node_modules/gatsby-cli/lib/reporter/redux/index.js:30:28)
at Array.forEach (<anonymous>)
at dispatch (/home//foo/broken-gatsby-develop-command/node_modules/gatsby-cli/lib/reporter/redux/index.js:30:12)
at Reporter.pendingActivity (/home//foo/broken-gatsby-develop-command/node_modules/redux/lib/redux.js:483:12)
at module.exports (/home//foo/broken-gatsby-develop-command/node_modules/gatsby/dist/commands/develop-process.js:413:21)
at Object.<anonymous> (/home//foo/broken-gatsby-develop-command/.cache/tmp-6512-KBLW7D8Kj2CY:4:5)
at Module._compile (internal/modules/cjs/loader.js:778:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
at Module.load (internal/modules/cjs/loader.js:653:32)
at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
gatsby@2.20.0 is not the latest version of Gatsby and as the last comment suggests a bug existed in the CLI, too. So I used gatsby new with the latest version of the gatsby-cli package and followed your steps, I don't see the error with the latest versions of everything. I'd suggest updating your packages :)
We're marking this issue as answered and closing it for now but please feel free to comment here if you would like to continue this discussion. We also recommend heading over to our communities if you have questions that are not bug reports or feature requests. We hope we managed to help and thank you for using Gatsby!
Hi @LekoArts! Thanks for your response. Unfortunately, it still doesn't work for me, even after upgrading gatsby, gatsby-cli and node. But I will move to one of the other issues. Sorry for not checking that more thoroughly before opening a new one!
Description
I upgraded
gatsby
and now I can't rungatsby develop
Steps to reproduce
gatsby new ...
gatsby develop
Here is a demo project: https://github.com/ehannes/broken-gatsby-develop-command.
Expected result
I would expect the command to run without a crash 😄
Actual result
It crashed with the following error:
Environment
Temporary fix
For me, it works to downgrade to gatsby
2.21.40
.The text was updated successfully, but these errors were encountered: