medium10 pts · first answer countsnextjsconfigurationdeployment

Changed env var, old value in browser

You change NEXT_PUBLIC_API_URL in the hosting dashboard and restart the running container without rebuilding. The browser still calls the old URL. Why?

A.The browser cached the environment variable in localStorageB.Restarting a container never reloads environment variables; you must delete and recreate itC.NEXT_PUBLIC_ values are inlined into the client bundle at build time, so you must rebuildD.Environment variables only apply to API routes

Discussion 0

Join free to post in the discussion.

Changed env var, old value in browser

Discussion 0

Related questions