Hi @followbl,
Pulling down local VERCEL_ environment variables for local development was removed because customers would sometimes edit these values locally and find themselves in confusing situations. These prefix variables are intended to only exist once code is deployed to the platform or when running a local environment intended to simulate the platform with vercel dev.
If you run vercel dev, environment variables that are knowable at local runtime should be available as part of the running process (for example, process.env in Node).
You should have access to VERCEL_URL, VERCEL_REGION, NOW_REGION, VERCEL_ENV, VERCEL.
For production, preview and we still allow pulling these locally for customers who have custom build requirements:
vercel env pull --environment production
vercel build --prod
vercel deploy --prod
So they’ll have them as part of their build, although do note many of the values will not be set (because they’re only known at the moment of deployment).
If you can tell us a bit more about your use case of wanting these available locally for development outside of use with vercel dev we can offer some suggestions.