This example demonstrates how to sync environment variables from your Vercel project to Trigger.dev.
trigger.config.ts file. This extension will then automatically run every time you deploy your Trigger.dev project.
VERCEL_ACCESS_TOKEN and VERCEL_PROJECT_ID environment variables, or pass
in the token and project ID as arguments to the syncVercelEnvVars build extension. If you’re
working with a team project, you’ll also need to set VERCEL_TEAM_ID, which can be found in your
team settings. You can find / generate the VERCEL_ACCESS_TOKEN in your Vercel
dashboard. Make sure the scope of the token covers
the project with the environment variables you want to sync.deploy command. You should see some output in the console indicating that the environment variables have been synced, and they should now be available in your Trigger.dev dashboard.