A monolithic repository, or monorepo, contains the code for many different projects in a single repository. To avoid confusion and possible conflicts with your dependencies, Gatsby recommends using npm for site development.Įngineers from Facebook, Google, Exponent, and Tilde launched Yarn in 2016 to improve package management for large-scale, monolithic repositories. Note: Most tutorials and site development examples from the Gatsby docs use npm. For Gatsby site development, you can use Yarn or npm. Gatsby theme development also uses Yarn workspaces. Gatsby core uses Yarn’s workspaces feature to manage dependencies. Contributing to Gatsby core requires Yarn. It’s an alternative to Node’s standard package manager, npm. Yarn is a package manager for the Node.js JavaScript runtime. So to get around this, I had to specify a specific version of C++ version to go get this to work.Learn what the Yarn package manager is, how to use it, and how it fits in to the Gatsby ecosystem. Essentially what we deduced is that I had previously upgraded NodeJS and the core libraries are now pointing to a newer version of C++. After a conversation with a good friend as well as some digging, we eventually found this StackOverflow post which helped us figure out what was going on. Gyp ERR! stack at Process.ChildProcess._handle.onexit (node:internal/child_process:290:12)Īnd it was baffling me quite a bit. Gyp ERR! stack at ChildProcess.emit (node:events:365:28)

Gyp ERR! stack at ChildProcess.onExit (/project_folder/node_modules/node-gyp/lib/build.js:262:23) Gyp ERR! stack Error: make failed with exit code: 2 Today, I got an error which I've never seen before and it looked like this: I typically jump around my ChromeOS and MacOS machines on a daily basis while I code.

Yarn install mac