Local dev server keeps crashing

[cesarvarela]

Starting a local server via gatsby develop or gatsby serve eventually leads to a heap memory crash. This gets in the way of development but, more importantly, causes a lot of flake during tests.

There is an open issue on Gatsby's repo that shows we are not the only ones getting these crashes, although the cause is not always the same:

• Heap memory usage increase during development builds after upgrading to v4.24.5 gatsbyjs/gatsby#36899

My current guess is that /api/* functions are leaking, not because of our implementation but because of how Gatsby handles them. So a way out of this could be to manage serving functions using Netlify (or Cloudflare) dev environment.

[cesarvarela]

Currently, Cloudflare does not support the entire Node API, so it is not usable for us to host the graphql endpoint.

https://developers.cloudflare.com/workers/runtime-apis/nodejs/

Besides that, even if they implemented the missing Node packages, they expect packages to be required using the node: prefix, which is at the moment incompatible with most packages we depend on.

Node.js APIs are available under the node: prefix, and this prefix must be used when importing modules, both in your code and the npm packages you depend on.