From 3c3898790b34d1bb7ee9508bf2be24f916d37788 Mon Sep 17 00:00:00 2001 From: D-K-P <8297864+D-K-P@users.noreply.github.com> Date: Fri, 12 Jun 2026 17:52:25 +0100 Subject: [PATCH 1/7] docs: redirect duplicate CLI command pages to canonical URLs --- docs/cli-deploy.mdx | 8 -------- docs/cli-dev.mdx | 8 -------- docs/cli-development-commands.mdx | 9 --------- docs/deploy-environment-variables.mdx | 2 +- docs/deployment/overview.mdx | 2 +- docs/docs.json | 14 +++++++++++++- docs/open-source-self-hosting.mdx | 2 +- docs/snippets/deplopying-your-task.mdx | 2 +- docs/snippets/useful-next-steps.mdx | 2 +- docs/tasks/scheduled.mdx | 4 ++-- docs/video-walkthrough.mdx | 2 +- 11 files changed, 21 insertions(+), 34 deletions(-) delete mode 100644 docs/cli-deploy.mdx delete mode 100644 docs/cli-dev.mdx delete mode 100644 docs/cli-development-commands.mdx diff --git a/docs/cli-deploy.mdx b/docs/cli-deploy.mdx deleted file mode 100644 index b9a8e087f29..00000000000 --- a/docs/cli-deploy.mdx +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "CLI deploy command" -description: "The `trigger.dev deploy` command can be used to deploy your tasks to our infrastructure." ---- - -import CliDeployCommands from "/snippets/cli-commands-deploy.mdx"; - - diff --git a/docs/cli-dev.mdx b/docs/cli-dev.mdx deleted file mode 100644 index d6e5fee10c3..00000000000 --- a/docs/cli-dev.mdx +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "CLI dev command" -description: "The `trigger.dev dev` command is used to run your tasks locally." ---- - -import CliDevCommands from "/snippets/cli-commands-develop.mdx"; - - \ No newline at end of file diff --git a/docs/cli-development-commands.mdx b/docs/cli-development-commands.mdx deleted file mode 100644 index 4a0f5384bf3..00000000000 --- a/docs/cli-development-commands.mdx +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "CLI development commands" -sidebarTitle: "Development commands" -description: "Use these commands to help develop your tasks locally." ---- - -import CliDevelopCommands from '/snippets/cli-commands-develop.mdx'; - - \ No newline at end of file diff --git a/docs/deploy-environment-variables.mdx b/docs/deploy-environment-variables.mdx index 529c621dec4..cd2dae1c81b 100644 --- a/docs/deploy-environment-variables.mdx +++ b/docs/deploy-environment-variables.mdx @@ -230,7 +230,7 @@ To sync environment variables from your Vercel projects to Trigger.dev, you can #### Deploy -When you run the [CLI deploy command](/cli-deploy) directly or using [GitHub Actions](/github-actions) it will sync the environment variables from [Infisical](https://infisical.com) to Trigger.dev. This means they'll appear on the Environment Variables page so you can confirm that it's worked. +When you run the [CLI deploy command](/cli-deploy-commands) directly or using [GitHub Actions](/github-actions) it will sync the environment variables from [Infisical](https://infisical.com) to Trigger.dev. This means they'll appear on the Environment Variables page so you can confirm that it's worked. This means that you need to redeploy your Trigger.dev tasks if you change the environment variables in [Infisical](https://infisical.com). diff --git a/docs/deployment/overview.mdx b/docs/deployment/overview.mdx index 8c15954cba8..103746ba09c 100644 --- a/docs/deployment/overview.mdx +++ b/docs/deployment/overview.mdx @@ -6,7 +6,7 @@ description: "Learn how to deploy your tasks to Trigger.dev." import CorepackError from "/snippets/corepack-error.mdx"; -Before you can run production workloads on Trigger.dev, you need to deploy your tasks. The only way to do this at the moment is through the [deploy CLI command](/cli-deploy): +Before you can run production workloads on Trigger.dev, you need to deploy your tasks. The only way to do this at the moment is through the [deploy CLI command](/cli-deploy-commands): diff --git a/docs/docs.json b/docs/docs.json index a926dcdadf4..301638c5bd9 100644 --- a/docs/docs.json +++ b/docs/docs.json @@ -195,7 +195,7 @@ { "group": "Development", "pages": [ - "cli-dev" + "cli-dev-commands" ] }, { @@ -746,6 +746,18 @@ ] }, "redirects": [ + { + "source": "/cli-dev", + "destination": "/cli-dev-commands" + }, + { + "source": "/cli-deploy", + "destination": "/cli-deploy-commands" + }, + { + "source": "/cli-development-commands", + "destination": "/cli-dev-commands" + }, { "source": "/v3/feature-matrix", "destination": "https://feedback.trigger.dev/roadmap" diff --git a/docs/open-source-self-hosting.mdx b/docs/open-source-self-hosting.mdx index ba5fc498701..0664b2c52d3 100644 --- a/docs/open-source-self-hosting.mdx +++ b/docs/open-source-self-hosting.mdx @@ -156,7 +156,7 @@ TRIGGER_DOMAIN=1234-42-42-42-42.ngrok-free.app ### Registry setup -If you want to deploy v3 projects, you will need access to a Docker registry. The [CLI deploy](/cli-deploy) command will push the images, and then the worker machine can pull them when needed. We will use Docker Hub as an example. +If you want to deploy v3 projects, you will need access to a Docker registry. The [CLI deploy](/cli-deploy-commands) command will push the images, and then the worker machine can pull them when needed. We will use Docker Hub as an example. 1. Sign up for a free account at [Docker Hub](https://hub.docker.com/) diff --git a/docs/snippets/deplopying-your-task.mdx b/docs/snippets/deplopying-your-task.mdx index 5414fc576fa..ade5e0a5db5 100644 --- a/docs/snippets/deplopying-your-task.mdx +++ b/docs/snippets/deplopying-your-task.mdx @@ -1,6 +1,6 @@ ## Deploying your task to Trigger.dev -For this guide, we'll manually deploy your task by running the [CLI deploy command](/cli-deploy) below. Other ways to deploy are listed in the next section. +For this guide, we'll manually deploy your task by running the [CLI deploy command](/cli-deploy-commands) below. Other ways to deploy are listed in the next section. diff --git a/docs/snippets/useful-next-steps.mdx b/docs/snippets/useful-next-steps.mdx index 8fdb53af199..7e7ef05a3e3 100644 --- a/docs/snippets/useful-next-steps.mdx +++ b/docs/snippets/useful-next-steps.mdx @@ -7,7 +7,7 @@ Learn how to write your own tasks - + Learn how to deploy your task manually using the CLI diff --git a/docs/tasks/scheduled.mdx b/docs/tasks/scheduled.mdx index cf3e6f050a6..a9dc3587d66 100644 --- a/docs/tasks/scheduled.mdx +++ b/docs/tasks/scheduled.mdx @@ -95,7 +95,7 @@ There are two ways of doing this: ### Declarative schedules -These sync when you run the [dev](/cli-dev) or [deploy](/cli-deploy) commands. +These sync when you run the [dev](/cli-dev-commands) or [deploy](/cli-deploy-commands) commands. To create them you add the `cron` property to your `schedules.task()`. This property is optional and is only used if you want to add a declarative schedule to your task: @@ -127,7 +127,7 @@ export const secondScheduledTask = schedules.task({ }); ``` -When you run the [dev](/cli-dev) or [deploy](/cli-deploy) commands, declarative schedules will be synced. If you add, delete or edit the `cron` property it will be updated when you run these commands. You can view your schedules on the Schedules page in the dashboard. +When you run the [dev](/cli-dev-commands) or [deploy](/cli-deploy-commands) commands, declarative schedules will be synced. If you add, delete or edit the `cron` property it will be updated when you run these commands. You can view your schedules on the Schedules page in the dashboard. ### Imperative schedules diff --git a/docs/video-walkthrough.mdx b/docs/video-walkthrough.mdx index 7da8e3f47ee..e8731cf5424 100644 --- a/docs/video-walkthrough.mdx +++ b/docs/video-walkthrough.mdx @@ -20,4 +20,4 @@ description: "Go from zero to a working task in your Next.js app in 10 minutes." - [1:44](https://youtu.be/YH_4c0K7fGM?si=J8svVzotZtyTXDap&t=104) – [Run and test](/run-tests) the "Hello, world!" example project - [2:09](https://youtu.be/YH_4c0K7fGM?si=FMTP8ep_cDBCU0_x&t=128) – Create and run an AI image generation task that uses [Fal.ai](https://fal.ai) – ([View the code](/guides/examples/fal-ai-image-to-cartoon)) - [6:25](https://youtu.be/YH_4c0K7fGM?si=pPc8iLI2Y9FGD3yo&t=385) – Create and run a [Realtime](/realtime/overview) example using [React hooks](/realtime/react-hooks) – ([View the code](/guides/examples/fal-ai-realtime)) -- [11:10](https://youtu.be/YH_4c0K7fGM?si=Mjd0EvvNsNlVouvY&t=670) – [Deploy your task](/cli-deploy) to the Trigger.dev Cloud +- [11:10](https://youtu.be/YH_4c0K7fGM?si=Mjd0EvvNsNlVouvY&t=670) – [Deploy your task](/cli-deploy-commands) to the Trigger.dev Cloud From 01bbd922fb1ff189bb3b1c913845fe7eb653cd99 Mon Sep 17 00:00:00 2001 From: D-K-P <8297864+D-K-P@users.noreply.github.com> Date: Wed, 17 Jun 2026 20:29:41 +0100 Subject: [PATCH 2/7] docs: make duplicate CLI page redirects permanent and drop duplicate nav entry --- docs/docs.json | 12 ++++-------- 1 file changed, 4 insertions(+), 8 deletions(-) diff --git a/docs/docs.json b/docs/docs.json index 301638c5bd9..2c90d92eb77 100644 --- a/docs/docs.json +++ b/docs/docs.json @@ -192,12 +192,6 @@ } ] }, - { - "group": "Development", - "pages": [ - "cli-dev-commands" - ] - }, { "group": "Deployment", "pages": [ @@ -748,11 +742,13 @@ "redirects": [ { "source": "/cli-dev", - "destination": "/cli-dev-commands" + "destination": "/cli-dev-commands", + "permanent": true }, { "source": "/cli-deploy", - "destination": "/cli-deploy-commands" + "destination": "/cli-deploy-commands", + "permanent": true }, { "source": "/cli-development-commands", From 79805f3ce76d1b9e32a00a3e57fa41485716abea Mon Sep 17 00:00:00 2001 From: D-K-P <8297864+D-K-P@users.noreply.github.com> Date: Wed, 17 Jun 2026 20:33:47 +0100 Subject: [PATCH 3/7] docs: unique titles for overview pages and descriptive intro anchors Three pages shared the title "Overview"; give building-with-ai, self-hosting/overview, and management/overview distinct titles (sidebar labels unchanged). Replace the generic "Learn more" links in the introduction build-extension table with descriptive anchor text. --- docs/building-with-ai.mdx | 2 +- docs/introduction.mdx | 26 +++++++++++++------------- docs/management/overview.mdx | 2 +- docs/self-hosting/overview.mdx | 3 ++- 4 files changed, 17 insertions(+), 16 deletions(-) diff --git a/docs/building-with-ai.mdx b/docs/building-with-ai.mdx index 710c9791eb3..7290a39b3e9 100644 --- a/docs/building-with-ai.mdx +++ b/docs/building-with-ai.mdx @@ -1,5 +1,5 @@ --- -title: "Overview" +title: "Building with AI: overview" sidebarTitle: "Overview" description: "Tools and resources for building Trigger.dev projects with AI coding assistants." --- diff --git a/docs/introduction.mdx b/docs/introduction.mdx index 383040de145..155965b2a73 100644 --- a/docs/introduction.mdx +++ b/docs/introduction.mdx @@ -91,19 +91,19 @@ We provide everything you need to build and manage background tasks: a CLI and S | Extension | What it does | Docs | | :-------------------- | :----------------------------------------------------------- | :----------------------------------------------------- | -| prismaExtension | Use Prisma with Trigger.dev | [Learn more](/config/extensions/prismaExtension) | -| pythonExtension | Execute Python scripts in Trigger.dev | [Learn more](/config/extensions/pythonExtension) | -| playwright | Use Playwright with Trigger.dev | [Learn more](/config/extensions/playwright) | -| puppeteer | Use Puppeteer with Trigger.dev | [Learn more](/config/extensions/puppeteer) | -| lightpanda | Use Lightpanda with Trigger.dev | [Learn more](/config/extensions/lightpanda) | -| ffmpeg | Use FFmpeg with Trigger.dev | [Learn more](/config/extensions/ffmpeg) | -| aptGet | Install system packages with aptGet | [Learn more](/config/extensions/aptGet) | -| additionalFiles | Copy additional files to the build directory | [Learn more](/config/extensions/additionalFiles) | -| additionalPackages | Include additional packages in the build | [Learn more](/config/extensions/additionalPackages) | -| syncEnvVars | Automatically sync environment variables to Trigger.dev | [Learn more](/config/extensions/syncEnvVars) | -| esbuildPlugin | Add existing or custom esbuild plugins to your build process | [Learn more](/config/extensions/esbuildPlugin) | -| emitDecoratorMetadata | Support for the emitDecoratorMetadata TypeScript compiler | [Learn more](/config/extensions/emitDecoratorMetadata) | -| audioWaveform | Support for Audio Waveform in your project | [Learn more](/config/extensions/audioWaveform) | +| prismaExtension | Use Prisma with Trigger.dev | [prismaExtension docs](/config/extensions/prismaExtension) | +| pythonExtension | Execute Python scripts in Trigger.dev | [pythonExtension docs](/config/extensions/pythonExtension) | +| playwright | Use Playwright with Trigger.dev | [playwright extension docs](/config/extensions/playwright) | +| puppeteer | Use Puppeteer with Trigger.dev | [puppeteer extension docs](/config/extensions/puppeteer) | +| lightpanda | Use Lightpanda with Trigger.dev | [lightpanda extension docs](/config/extensions/lightpanda) | +| ffmpeg | Use FFmpeg with Trigger.dev | [ffmpeg extension docs](/config/extensions/ffmpeg) | +| aptGet | Install system packages with aptGet | [aptGet extension docs](/config/extensions/aptGet) | +| additionalFiles | Copy additional files to the build directory | [additionalFiles docs](/config/extensions/additionalFiles) | +| additionalPackages | Include additional packages in the build | [additionalPackages docs](/config/extensions/additionalPackages) | +| syncEnvVars | Automatically sync environment variables to Trigger.dev | [syncEnvVars docs](/config/extensions/syncEnvVars) | +| esbuildPlugin | Add existing or custom esbuild plugins to your build process | [esbuildPlugin docs](/config/extensions/esbuildPlugin) | +| emitDecoratorMetadata | Support for the emitDecoratorMetadata TypeScript compiler | [emitDecoratorMetadata docs](/config/extensions/emitDecoratorMetadata) | +| audioWaveform | Support for Audio Waveform in your project | [audioWaveform docs](/config/extensions/audioWaveform) | ## Explore by example diff --git a/docs/management/overview.mdx b/docs/management/overview.mdx index 4f3316a32bd..1911fb139da 100644 --- a/docs/management/overview.mdx +++ b/docs/management/overview.mdx @@ -1,5 +1,5 @@ --- -title: Overview +title: "Management API overview" sidebarTitle: Overview description: Using the Trigger.dev management API --- diff --git a/docs/self-hosting/overview.mdx b/docs/self-hosting/overview.mdx index ecc975a5a7f..91c7d19a3d7 100644 --- a/docs/self-hosting/overview.mdx +++ b/docs/self-hosting/overview.mdx @@ -1,5 +1,6 @@ --- -title: "Overview" +title: "Self-hosting overview" +sidebarTitle: "Overview" description: "You can self-host Trigger.dev on your own infrastructure." --- From 2d635b590ca940c6429cfa233054e3e95a6907b1 Mon Sep 17 00:00:00 2001 From: D-K-P <8297864+D-K-P@users.noreply.github.com> Date: Wed, 17 Jun 2026 20:34:04 +0100 Subject: [PATCH 4/7] docs: fix https links, a Discord link, and missing page descriptions Rewrite two cloud.trigger.dev links from http to https in the Supabase edge-function guides. Point the troubleshooting page's help link to Discord instead of GitHub issues. Add missing description frontmatter to three troubleshooting and help pages. --- docs/guides/frameworks/supabase-edge-functions-basic.mdx | 2 +- .../frameworks/supabase-edge-functions-database-webhooks.mdx | 2 +- docs/help-slack.mdx | 1 + docs/troubleshooting-debugging-in-vscode.mdx | 1 + docs/troubleshooting-github-issues.mdx | 2 +- docs/troubleshooting-uptime-status.mdx | 1 + 6 files changed, 6 insertions(+), 3 deletions(-) diff --git a/docs/guides/frameworks/supabase-edge-functions-basic.mdx b/docs/guides/frameworks/supabase-edge-functions-basic.mdx index c3372c41e94..2aac0d789ec 100644 --- a/docs/guides/frameworks/supabase-edge-functions-basic.mdx +++ b/docs/guides/frameworks/supabase-edge-functions-basic.mdx @@ -185,7 +185,7 @@ Once loaded you should see ‘OK’ on the new screen. The task will be triggered when your edge function URL is accessed. -Check your [cloud.trigger.dev](http://cloud.trigger.dev) dashboard and you should see a succesful `hello-world` task. +Check your [cloud.trigger.dev](https://cloud.trigger.dev) dashboard and you should see a succesful `hello-world` task. **Congratulations, you have run a simple Hello World task from a Supabase edge function!** diff --git a/docs/guides/frameworks/supabase-edge-functions-database-webhooks.mdx b/docs/guides/frameworks/supabase-edge-functions-database-webhooks.mdx index 4114e95ef9c..a2d13863508 100644 --- a/docs/guides/frameworks/supabase-edge-functions-database-webhooks.mdx +++ b/docs/guides/frameworks/supabase-edge-functions-database-webhooks.mdx @@ -422,7 +422,7 @@ You can use the following public video URL for testing: `https://content.trigger ![How to insert a new row 2](/images/supabase-new-table-4.png) -Once the new table row has been inserted, check your [cloud.trigger.dev](http://cloud.trigger.dev) project 'Runs' list and you should see a processing `videoProcessAndUpdate` task which has been triggered when you added a new row with the video url to your `video_transcriptions` table. +Once the new table row has been inserted, check your [cloud.trigger.dev](https://cloud.trigger.dev) project 'Runs' list and you should see a processing `videoProcessAndUpdate` task which has been triggered when you added a new row with the video url to your `video_transcriptions` table. ![Supabase successful run](/images/supabase-run-result.png) diff --git a/docs/help-slack.mdx b/docs/help-slack.mdx index 0b733522ac2..917e77a0627 100644 --- a/docs/help-slack.mdx +++ b/docs/help-slack.mdx @@ -1,5 +1,6 @@ --- title: "Slack support" +description: "Trigger.dev Pro plan customers can request a private Slack Connect channel for support." --- If you're on the Trigger.dev Pro plan, you can request a private Slack Connect channel. diff --git a/docs/troubleshooting-debugging-in-vscode.mdx b/docs/troubleshooting-debugging-in-vscode.mdx index 516e1152940..b9d01ef6054 100644 --- a/docs/troubleshooting-debugging-in-vscode.mdx +++ b/docs/troubleshooting-debugging-in-vscode.mdx @@ -1,6 +1,7 @@ --- title: "Debugging in VS Code" sidebarTitle: "Debugging in VS Code" +description: "Attach the VS Code debugger to your Trigger.dev tasks to set breakpoints and step through your code." --- import DebuggingInVSCode from '/snippets/debugging_in_vscode.mdx'; diff --git a/docs/troubleshooting-github-issues.mdx b/docs/troubleshooting-github-issues.mdx index 51052d4d53b..3e84c7365b2 100644 --- a/docs/troubleshooting-github-issues.mdx +++ b/docs/troubleshooting-github-issues.mdx @@ -3,4 +3,4 @@ title: "GitHub Issues" url: "https://github.com/triggerdotdev/trigger.dev/issues" --- -Please [join our community on Discord](https://github.com/triggerdotdev/trigger.dev/issues) to ask questions, share your projects, and get help from other developers. +Please [join our community on Discord](https://trigger.dev/discord) to report bugs, request features, or get help from the team and other developers. diff --git a/docs/troubleshooting-uptime-status.mdx b/docs/troubleshooting-uptime-status.mdx index 0890887f5b7..6f57950708e 100644 --- a/docs/troubleshooting-uptime-status.mdx +++ b/docs/troubleshooting-uptime-status.mdx @@ -1,5 +1,6 @@ --- title: "Uptime Status" +description: "Subscribe to email notifications for Trigger.dev platform incidents and status updates." --- Get email notifications when Trigger.dev creates, updates or resolves a platform incident. From a974a4ad162f866ca6707fb7e2fa7fd95244aa51 Mon Sep 17 00:00:00 2001 From: D-K-P <8297864+D-K-P@users.noreply.github.com> Date: Thu, 18 Jun 2026 12:34:31 +0100 Subject: [PATCH 5/7] docs: make deleted CLI redirect permanent and fix a typo Add permanent: true to the /cli-development-commands redirect so it returns a 301 like the other deleted CLI pages. Fix 'succesful' to 'successful' in the Supabase edge functions guide. --- docs/docs.json | 3 ++- docs/guides/frameworks/supabase-edge-functions-basic.mdx | 2 +- 2 files changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/docs.json b/docs/docs.json index 2c90d92eb77..77269340944 100644 --- a/docs/docs.json +++ b/docs/docs.json @@ -752,7 +752,8 @@ }, { "source": "/cli-development-commands", - "destination": "/cli-dev-commands" + "destination": "/cli-dev-commands", + "permanent": true }, { "source": "/v3/feature-matrix", diff --git a/docs/guides/frameworks/supabase-edge-functions-basic.mdx b/docs/guides/frameworks/supabase-edge-functions-basic.mdx index 2aac0d789ec..3da85257e7c 100644 --- a/docs/guides/frameworks/supabase-edge-functions-basic.mdx +++ b/docs/guides/frameworks/supabase-edge-functions-basic.mdx @@ -185,7 +185,7 @@ Once loaded you should see ‘OK’ on the new screen. The task will be triggered when your edge function URL is accessed. -Check your [cloud.trigger.dev](https://cloud.trigger.dev) dashboard and you should see a succesful `hello-world` task. +Check your [cloud.trigger.dev](https://cloud.trigger.dev) dashboard and you should see a successful `hello-world` task. **Congratulations, you have run a simple Hello World task from a Supabase edge function!** From 535be812aa42b515db1615a5c7db4797e05cebc3 Mon Sep 17 00:00:00 2001 From: D-K-P <8297864+D-K-P@users.noreply.github.com> Date: Thu, 18 Jun 2026 12:34:41 +0100 Subject: [PATCH 6/7] docs: repoint dead external links in guides Update three 404'd external links to their current URLs: the Replicate nano-banana model, the LibreOffice download page, and the Anchor Browser docs. --- docs/guides/example-projects/anchor-browser-web-scraper.mdx | 2 +- docs/guides/examples/libreoffice-pdf-conversion.mdx | 2 +- docs/guides/examples/replicate-image-generation.mdx | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/guides/example-projects/anchor-browser-web-scraper.mdx b/docs/guides/example-projects/anchor-browser-web-scraper.mdx index 1bdd8b5d456..fc714f963b5 100644 --- a/docs/guides/example-projects/anchor-browser-web-scraper.mdx +++ b/docs/guides/example-projects/anchor-browser-web-scraper.mdx @@ -119,6 +119,6 @@ export default defineConfig({ ## Learn more -- View the [Anchor Browser docs](https://anchorbrowser.io/docs) to learn more about Anchor Browser's AI-powered browser automation tools. +- View the [Anchor Browser docs](https://docs.anchorbrowser.io/) to learn more about Anchor Browser's AI-powered browser automation tools. - Check out the source code for the [Anchor Browser web scraper repo](https://github.com/triggerdotdev/examples/tree/main/anchor-browser-web-scraper) on GitHub. - Browser our [example projects](/guides/introduction) to see how you can use Trigger.dev with other services. diff --git a/docs/guides/examples/libreoffice-pdf-conversion.mdx b/docs/guides/examples/libreoffice-pdf-conversion.mdx index bec9f1e0645..024b3a2b387 100644 --- a/docs/guides/examples/libreoffice-pdf-conversion.mdx +++ b/docs/guides/examples/libreoffice-pdf-conversion.mdx @@ -9,7 +9,7 @@ import LocalDevelopment from "/snippets/local-development-extensions.mdx"; ## Prerequisites - A project with [Trigger.dev initialized](/quick-start) -- [LibreOffice](https://www.libreoffice.org/download/libreoffice-fresh/) installed on your machine +- [LibreOffice](https://www.libreoffice.org/download/download-libreoffice/) installed on your machine - A [Cloudflare R2](https://developers.cloudflare.com) account and bucket ### Using our `aptGet` build extension to add the LibreOffice package diff --git a/docs/guides/examples/replicate-image-generation.mdx b/docs/guides/examples/replicate-image-generation.mdx index 756a518ff78..7de00ac568b 100644 --- a/docs/guides/examples/replicate-image-generation.mdx +++ b/docs/guides/examples/replicate-image-generation.mdx @@ -6,7 +6,7 @@ description: "Learn how to generate images from source image URLs using Replicat ## Overview -This example demonstrates how to use Trigger.dev to generate images from source image URLs using [Replicate](https://replicate.com/), the [nano-banana-image-to-image](https://replicate.com/meta/nano-banana-image-to-image) model. +This example demonstrates how to use Trigger.dev to generate images from source image URLs using [Replicate](https://replicate.com/), the [nano-banana](https://replicate.com/google/nano-banana) model. ## Task code From 2161c0b253632aaa54577ebddb7b2e4188f4fa9a Mon Sep 17 00:00:00 2001 From: D-K-P <8297864+D-K-P@users.noreply.github.com> Date: Thu, 18 Jun 2026 12:41:19 +0100 Subject: [PATCH 7/7] docs: fix variable shadowing in management API overview example The list example declared `const runs = await runs.list(...)`, which shadowed the imported `runs` and threw at runtime. Rename the local to `completedRuns`. --- docs/management/overview.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/management/overview.mdx b/docs/management/overview.mdx index 1911fb139da..0f64e505727 100644 --- a/docs/management/overview.mdx +++ b/docs/management/overview.mdx @@ -37,7 +37,7 @@ configure({ }); async function main() { - const runs = await runs.list({ + const completedRuns = await runs.list({ limit: 10, status: ["COMPLETED"], });