I'm on Next JS 14, pages router. Pages router, so I'm using next-runtime-env 1.8
In my Dockerfile, I do next build. In CI, I see it say that it skips my variable with a message like this:
warn [next-runtime-env] skipped prefixing environment variable '<my var>'. Variable not in process.env.
When I go to my deployed website, the __ENV.js is empty, it just has window.__ENV = {};
Is it empty because the env variable is missing at build time? Isn't the whole point of this library to allow you to not have these environments at build time?
I'm on Next JS 14, pages router. Pages router, so I'm using next-runtime-env 1.8
In my Dockerfile, I do
next build. In CI, I see it say that it skips my variable with a message like this:warn [next-runtime-env] skipped prefixing environment variable '<my var>'. Variable not in process.env.When I go to my deployed website, the __ENV.js is empty, it just has
window.__ENV = {};Is it empty because the env variable is missing at build time? Isn't the whole point of this library to allow you to not have these environments at build time?