[hydrogen] Polyfill Oxygen global in Hydrogen

[mperreux]

Related Issues

Description stolen from #8413
It's currently not possible to access environment variables in Hydrogen projects deployed to Vercel. The reason is that Hydrogen currently relies on a global Oxygen.env that needs to be polyfilled in the platform. This PR adds the global object using process.env, which is mentioned in the docs as the way to access environment variables in Edge Functions.

📋 Checklist

Tests

• The code changed/added as part of this PR has been covered with tests
• All tests pass locally with yarn test-unit

Code Review

• This PR has a concise title and thorough description useful to a reviewer
• Issue from task tracker has a link to this PR

[TooTallNate]

Unfortunately I actually think that this won't work the way you're expecting. This is because for Edge functions, process.env usage is statically analyzed to determine which variables to include in the edge function bundle.

To make it work with Oxygen.env usage then we would have to do similar static analysis in @vercel/hydrogen and populate the envVarsInUse array in the EdgeFunction constructor. Perhaps Hydrogen could provide that information if it is already doing static analysis during the build process?

[frandiox]

We're not doing any static analysis in the build process in Hydrogen, afaik 🤔
Perhaps you can replace Oxygen.env.XYZ matches in @vercel/hydrogen?

Also, we are moving to using Hydrogen.env instead of Oxygen.env to avoid confusion when deploying to other platforms, so something to keep in mind.

[ryanleichty]

Any idea when this might get merged/resolved? Would love to use Vercel for hosting a current project 🙌🏻

[TooTallNate]

@ryanleichty The current workaround would be to just use process.env instead.