Fix for "vercel dev" pulling too much environment

Issue 17557 describes a situation where "vercel dev" pulls all environment variables across all branches, leading to a failure to start because the environment is too big (E2BIG error).

Per the contribution guidelines, I'm here to propose a fix, which is as follows:

src/commands/dev/dev.ts:156 — current: envValues = (await pullEnvRecords(client, project.id, 'vercel-cli:dev')) .env;

Proposed: envValues = ( await pullEnvRecords(client, project.id, 'vercel-cli:dev', { target: 'development', }) ).env;

The current code has no target, and so I believe ends up pulling variables across all targets. The new code should just pull the development variables.

Any concerns with this approach to fixing?

Andrew

Um.... ignore this for now. I can no longer reproduce it, and pullEnvRecords apparently does the right thing (initial analysis was wrong). I'm not sure if there was a server change that caused this or not. I've closed the issue and will monitor on our end.

vercel dev shouldn't be pulling anything automatically, if you want to get the latest env vars you need to use either vercel pull(which pulls into a .vercel directory)

Or I prefer using the more specific vercel env pull which only pulls my .env.local file

Were you using one of those when you ran into the issue?