这是indexloc提供的服务,不要输入任何密码
Skip to content

Add default env vars #1322

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jun 2, 2022
Merged

Add default env vars #1322

merged 2 commits into from
Jun 2, 2022

Conversation

gsoltis
Copy link
Contributor

@gsoltis gsoltis commented Jun 1, 2022

The first candidate is VERCEL_ANALYTICS_ID

@vercel
Copy link

vercel bot commented Jun 1, 2022

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment
Name Status Preview Updated
turbo-site ⬜️ Ignored (Inspect) Jun 1, 2022 at 11:42PM (UTC)

@gsoltis gsoltis marked this pull request as ready for review June 1, 2022 23:36
@kodiakhq kodiakhq bot merged commit 1a046a0 into main Jun 2, 2022
@kodiakhq kodiakhq bot deleted the gsoltis/default_env_vars branch June 2, 2022 00:07
@nathanhammond
Copy link
Contributor

When we get back to making sure that we play nicely with all the things, we should scope this down to just nodes in the graph that VERCEL_ANALYTICS_ID would be relevant for: build for ["next", "nuxt", "gatsby"]

For Vercel Projects that enable Vercel Analytics this is a full partition of the cache between Prod and Dev of all Turborepo DAG nodes, no matter what they do, not just the limited set of build for ["next", "nuxt", "gatsby"] and their children.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants