4 Replies
Ah that is a bug in the node compatibility layer in deno. Looks like it tries to access the
process
global before it's set as a global. I got a fix working locallyooh, please tell me ty
Made a PR with the fix here https://github.com/denoland/deno/pull/19184