You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Having to run build-local just to bake some environment vars into the UIs is very annoying.
There is no reason the UIs cannot pull these at runtime from env vars like the backend does.
The text was updated successfully, but these errors were encountered:
Hi @etiennea definitely agree, unfortunately with Next.js it isn't super straightforward to have the variables baked dynamically and we have yet to find a straightforward solution to do so. We're open to ideas/approaches on how to improve this (or even PRs). We've evaluated using packages such as next-runtime-env and some other workarounds to no success so far.
Just linking this with #12 where we've had some prior conversations around this.
Having to run build-local just to bake some environment vars into the UIs is very annoying.
There is no reason the UIs cannot pull these at runtime from env vars like the backend does.
The text was updated successfully, but these errors were encountered: