Not finding them locally might confuse people (e.g. https://github.com/cloudflare/next-on-pages/issues/758) and we should always strive for parity between local and prod, so ideally we should add some mocks for such values in getPlatformProxy, similarly to how Astro used to.
Notes/Questions:
the variables should naturally be only populated if the target application is a Pages one (an extra flag to signal getPlatformProxy when the target application is a Pages one, as mentioned in https://github.com/cloudflare/workers-sdk/issues/5742 could come in handy here... 🤔)
petebacondarwin
commented
3 months ago
Describe the solution
getPlatformProxydoesn't populate the Pages injected environment variables meaning that those are only available in production.Not finding them locally might confuse people (e.g. https://github.com/cloudflare/next-on-pages/issues/758) and we should always strive for parity between local and prod, so ideally we should add some mocks for such values in
getPlatformProxy, similarly to how Astro used to.Notes/Questions:
getPlatformProxywhen the target application is a Pages one, as mentioned in https://github.com/cloudflare/workers-sdk/issues/5742 could come in handy here... 🤔)ASSETSbinding also be included?