Part of our "Framework Defined Infrastructure" mantra at Vercel is that we don't treat frameworks as black boxes. Respectively, we can also warn you if you do something that is potentially dangerous but only if combined with framework X
Environment variables with certain framework-specific prefixes now show guidance that the value will be exposed to the client. For example, `NEXT_PUBLIC_`, `NUXT_ENV_`, or `VITE_`. vercel.com/changelog/publ…