diff --git a/docs/config/extensions/lightpanda.mdx b/docs/config/extensions/lightpanda.mdx
index 0408d45ad5..1e1efc8f63 100644
--- a/docs/config/extensions/lightpanda.mdx
+++ b/docs/config/extensions/lightpanda.mdx
@@ -5,10 +5,6 @@ description: "Use the lightpanda build extension to add Lightpanda browser to yo
tag: "v4"
---
-import UpgradeToV4Note from "/snippets/upgrade-to-v4-note.mdx";
-
-
-
To use the Lightpanda browser in your project, add the extension to your `trigger.config.ts` file:
```ts trigger.config.ts
diff --git a/docs/guides/examples/lightpanda.mdx b/docs/guides/examples/lightpanda.mdx
index 9eab531176..d2a431624e 100644
--- a/docs/guides/examples/lightpanda.mdx
+++ b/docs/guides/examples/lightpanda.mdx
@@ -6,9 +6,6 @@ tag: "v4"
---
import ScrapingWarning from "/snippets/web-scraping-warning.mdx";
-import UpgradeToV4Note from "/snippets/upgrade-to-v4-note.mdx";
-
-
## Overview
diff --git a/docs/guides/frameworks/bun.mdx b/docs/guides/frameworks/bun.mdx
index 0d369fbf98..e5f4ab1cd0 100644
--- a/docs/guides/frameworks/bun.mdx
+++ b/docs/guides/frameworks/bun.mdx
@@ -1,7 +1,7 @@
---
title: "Bun guide"
sidebarTitle: "Bun"
-description: "This guide will show you how to setup Trigger.dev with Bun"
+description: "This guide will show you how to setup Trigger.dev in your existing Bun project, test an example task, and view the run."
icon: "js"
---
@@ -9,17 +9,17 @@ import Prerequisites from "/snippets/framework-prerequisites.mdx";
import CliRunTestStep from "/snippets/step-run-test.mdx";
import CliViewRunStep from "/snippets/step-view-run.mdx";
-A specific Bun version is currently required for the dev command to work. This is due to a [bug](https://github.com/oven-sh/bun/issues/13799) with IPC. Please use Bun version 1.1.24 or lower: `curl -fsSL https://bun.sh/install | bash -s -- bun-v1.1.24`
-
-We now have experimental support for Bun. This guide will show you have to setup Trigger.dev in your existing Bun project, test an example task, and view the run.
-
-
- The trigger.dev CLI does not yet support Bun. So you will need to run the CLI using Node.js. But
+
+ The trigger.dev CLI does not yet support Bun. So you will need to run the CLI using Node.js.
Bun will still be used to execute your tasks, even in the `dev` environment.
-
+
+## Known issues
+
+- Certain OpenTelemetry instrumentation will not work with Bun, because Bun does not support Node's `register` hook. This means that some libraries that rely on this hook will not work with Bun.
+
## Initial setup
@@ -109,7 +109,3 @@ yarn dlx trigger.dev@latest dev
-
-## Known issues
-
-- Certain OpenTelemetry instrumentation will not work with Bun, because Bun does not support Node's `register` hook. This means that some libraries that rely on this hook will not work with Bun.
diff --git a/docs/guides/frameworks/nextjs.mdx b/docs/guides/frameworks/nextjs.mdx
index 78a54b7c21..d8b35cbe64 100644
--- a/docs/guides/frameworks/nextjs.mdx
+++ b/docs/guides/frameworks/nextjs.mdx
@@ -14,7 +14,6 @@ import UsefulNextSteps from "/snippets/useful-next-steps.mdx";
import TriggerTaskNextjs from "/snippets/trigger-tasks-nextjs.mdx";
import NextjsTroubleshootingMissingApiKey from "/snippets/nextjs-missing-api-key.mdx";
import NextjsTroubleshootingButtonSyntax from "/snippets/nextjs-button-syntax.mdx";
-import WorkerFailedToStartWhenRunningDevCommand from "/snippets/worker-failed-to-start.mdx";
import AddEnvironmentVariables from "/snippets/add-environment-variables.mdx";
import DeployingYourTask from "/snippets/deplopying-your-task.mdx";
import VercelDocsCards from "/snippets/vercel-docs-cards.mdx";
@@ -432,7 +431,6 @@ You can test your revalidation task in the Trigger.dev dashboard on the testing
-
diff --git a/docs/guides/frameworks/supabase-edge-functions-basic.mdx b/docs/guides/frameworks/supabase-edge-functions-basic.mdx
index f848f05000..db050292ff 100644
--- a/docs/guides/frameworks/supabase-edge-functions-basic.mdx
+++ b/docs/guides/frameworks/supabase-edge-functions-basic.mdx
@@ -14,7 +14,6 @@ import UsefulNextSteps from "/snippets/useful-next-steps.mdx";
import TriggerTaskNextjs from "/snippets/trigger-tasks-nextjs.mdx";
import NextjsTroubleshootingMissingApiKey from "/snippets/nextjs-missing-api-key.mdx";
import NextjsTroubleshootingButtonSyntax from "/snippets/nextjs-button-syntax.mdx";
-import WorkerFailedToStartWhenRunningDevCommand from "/snippets/worker-failed-to-start.mdx";
import SupabaseDocsCards from "/snippets/supabase-docs-cards.mdx";
import SupabaseAuthInfo from "/snippets/supabase-auth-info.mdx";
diff --git a/docs/guides/frameworks/supabase-edge-functions-database-webhooks.mdx b/docs/guides/frameworks/supabase-edge-functions-database-webhooks.mdx
index 89f31b4b53..81b04cae6d 100644
--- a/docs/guides/frameworks/supabase-edge-functions-database-webhooks.mdx
+++ b/docs/guides/frameworks/supabase-edge-functions-database-webhooks.mdx
@@ -10,7 +10,6 @@ import UsefulNextSteps from "/snippets/useful-next-steps.mdx";
import TriggerTaskNextjs from "/snippets/trigger-tasks-nextjs.mdx";
import NextjsTroubleshootingMissingApiKey from "/snippets/nextjs-missing-api-key.mdx";
import NextjsTroubleshootingButtonSyntax from "/snippets/nextjs-button-syntax.mdx";
-import WorkerFailedToStartWhenRunningDevCommand from "/snippets/worker-failed-to-start.mdx";
import SupabaseDocsCards from "/snippets/supabase-docs-cards.mdx";
import SupabaseAuthInfo from "/snippets/supabase-auth-info.mdx";