Astro can't access process global

[EdamAme-x]

It can create compatibility with many frameworks.

Ex.

Deno.env.get("NODE_ENV") === process.env.NODE_ENV

[EdamAme-x]

ref

deno/ext/node/polyfills/_process/process.ts

Line 38 in 3341c50

/** Wrapper of Deno.env.get, which doesn't throw type error when

[bartlomieju]

Can you elaborate what's the ask here?

[EdamAme-x]

hi @bartlomieju
Thanks for your reply.

I think node:process should be the standard global object (or optional with flag).
This should allow Astro to work fully with the Deno itself, including the hydrate process.

Astro is using node:process in global

[bartlomieju]

We are not going to expose process as a global object in user code, but the NPM packages should have it available. If it doesn't work with Astro it's a bug. Do you have a reproduction that currently doesn't work correctly?

[EdamAme-x]

thanks for the reply.
It can be reproduced by creating a normal Astro app with bun and running astro dev with deno. Normally this does not happen, but if you add an integration such as react, you will get a reference error in component-render.js that the process does not exist.

[bartlomieju]

How do you run the app? Please try running with DENO_FUTURE=1 env var set up.

[EdamAme-x]

it works! thanks bro!!! @bartlomieju