Updated vercel env vars instructions and naming

Author: D-K-P

docs/config/config-file.mdx

@@ -505,27 +505,28 @@ export default defineConfig({
 });
 ```
 
-#### vercelSyncEnvVars
+#### syncVercelEnvVars
 
-The `vercelSyncEnvVars` build extension syncs environment variables from your Vercel project to Trigger.dev.
+The `syncVercelEnvVars` build extension syncs environment variables from your Vercel project to Trigger.dev.
 
 <Note>
   You need to set the `VERCEL_ACCESS_TOKEN` and `VERCEL_PROJECT_ID` environment variables, or pass
-  in the token and project ID as arguments to the `vercelSyncEnvVars` build extension. If you're
-  working with a team project, you'll also need to set `VERCEL_TEAM_ID`. You can find / generate
-  the `VERCEL_ACCESS_TOKEN` in your Vercel [dashboard](https://vercel.com/account/settings/tokens).
-  Make sure the scope of the token covers the project you want to sync.
+  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](https://vercel.com/account/settings/tokens). Make sure the scope of the token covers
+  the project with the environment variables you want to sync.
 </Note>
 
 ```ts
 import { defineConfig } from "@trigger.dev/sdk/v3";
-import { vercelSyncEnvVars } from "@trigger.dev/build/extensions/core";
+import { syncVercelEnvVars } from "@trigger.dev/build/extensions/core";
 
 export default defineConfig({
   project: "<project ref>",
   // Your other config settings...
   build: {
-    extensions: [vercelSyncEnvVars()],
+    extensions: [syncVercelEnvVars()],
   },
 });
 ```

docs/guides/examples/vercel-sync-env-vars.mdx

@@ -11,24 +11,24 @@ import VercelDocsCards from "/snippets/vercel-docs-cards.mdx";
 To sync environment variables, you just need to add our build extension to your `trigger.config.ts` file. This extension will then automatically run every time you deploy your Trigger.dev project.
 
 <Note>
-  You need to set the `VERCEL_ACCESS_TOKEN` and `VERCEL_PROJECT_ID` environment variables in the
-  Trigger.dev dashboard, or pass in the token and project ID as arguments to the `vercelSyncEnvVars`
-  build extension. If you're working with a team project, you'll also need to set `VERCEL_TEAM_ID`. 
-  You can find / generate the `VERCEL_ACCESS_TOKEN` in your Vercel
+  You need to set the `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](https://vercel.com/account/settings/tokens). Make sure the scope of the token covers
   the project with the environment variables you want to sync.
 </Note>
 
 ```ts trigger.config.ts
 import { defineConfig } from "@trigger.dev/sdk/v3";
-import { vercelSyncEnvVars } from "@trigger.dev/build/extensions/core";
+import { syncVercelEnvVars } from "@trigger.dev/build/extensions/core";
 
 export default defineConfig({
   project: "<project ref>",
   // Your other config settings...
   build: {
-    // Add the vercelSyncEnvVars build extension
-    extensions: [vercelSyncEnvVars()],
+    // Add the syncVercelEnvVars build extension
+    extensions: [syncVercelEnvVars()],
   },
 });
 ```

docs/guides/frameworks/nextjs.mdx

@@ -247,25 +247,26 @@ Here are the steps to trigger your task in the Next.js App and Pages router and
 
 ## Automatically sync environment variables from your Vercel project (optional)
 
-If you want to automatically sync environment variables from your Vercel project to Trigger.dev, you can add our `vercelSyncEnvVars` build extension to your `trigger.config.ts` file.
+If you want to automatically sync environment variables from your Vercel project to Trigger.dev, you can add our `syncVercelEnvVars` build extension to your `trigger.config.ts` file.
 
 <Note>
   You need to set the `VERCEL_ACCESS_TOKEN` and `VERCEL_PROJECT_ID` environment variables, or pass
-  in the token and project ID as arguments to the `vercelSyncEnvVars` build extension. If you're
-  working with a team project, you'll also need to set `VERCEL_TEAM_ID`. You can find / generate
-  the `VERCEL_ACCESS_TOKEN` in your Vercel [dashboard](https://vercel.com/account/settings/tokens).
-  Make sure the scope of the token covers the project you want to sync.
+  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](https://vercel.com/account/settings/tokens). Make sure the scope of the token covers
+  the project with the environment variables you want to sync.
 </Note>
 
 ```ts trigger.config.ts
 import { defineConfig } from "@trigger.dev/sdk/v3";
-import { vercelSyncEnvVars } from "@trigger.dev/build/extensions/core";
+import { syncVercelEnvVars } from "@trigger.dev/build/extensions/core";
 
 export default defineConfig({
   project: "<project ref>",
   // Your other config settings...
   build: {
-    extensions: [vercelSyncEnvVars()],
+    extensions: [syncVercelEnvVars()],
   },
 });
 ```

packages/build/src/extensions/core.ts

@@ -3,4 +3,4 @@ export * from "./core/additionalPackages.js";
 export * from "./core/syncEnvVars.js";
 export * from "./core/aptGet.js";
 export * from "./core/ffmpeg.js";
-export * from "./core/vercelSyncEnvVars.js";
+export * from "./core/syncVercelEnvVars.js";

packages/build/src/extensions/core/vercelSyncEnvVars.ts

@@ -1,8 +1,12 @@
 import { BuildExtension } from "@trigger.dev/core/v3/build";
 import { syncEnvVars } from "../core.js";
 
-export function vercelSyncEnvVars(
-  options?: { projectId?: string; vercelAccessToken?: string; vercelTeamId?: string },
+export function syncVercelEnvVars(
+  options?: {
+    projectId?: string;
+    vercelAccessToken?: string;
+    vercelTeamId?: string;
+  },
 ): BuildExtension {
   const sync = syncEnvVars(async (ctx) => {
     const projectId = options?.projectId ?? process.env.VERCEL_PROJECT_ID ??
@@ -15,13 +19,13 @@ export function vercelSyncEnvVars(
 
     if (!projectId) {
       throw new Error(
-        "vercelSyncEnvVars: you did not pass in a projectId or set the VERCEL_PROJECT_ID env var.",
+        "syncVercelEnvVars: you did not pass in a projectId or set the VERCEL_PROJECT_ID env var.",
       );
     }
 
     if (!vercelAccessToken) {
       throw new Error(
-        "vercelSyncEnvVars: you did not pass in a vercelAccessToken or set the VERCEL_ACCESS_TOKEN env var.",
+        "syncVercelEnvVars: you did not pass in a vercelAccessToken or set the VERCEL_ACCESS_TOKEN env var.",
       );
     }
 
@@ -41,7 +45,8 @@ export function vercelSyncEnvVars(
     }
     const params = new URLSearchParams({ decrypt: "true" });
     if (vercelTeamId) params.set("teamId", vercelTeamId);
-    const vercelApiUrl = `https://api.vercel.com/v8/projects/${projectId}/env?${params}`;
+    const vercelApiUrl =
+      `https://api.vercel.com/v8/projects/${projectId}/env?${params}`;
 
     try {
       const response = await fetch(vercelApiUrl, {