You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit a8a8785
Browse filesBrowse the repository at this point in the historyBrowse files
feat(core,cli,supervisor): bun-1.4 runtime (node-less, Bun 1.4.4) plus a bun-legacy alias
Adds the `bun-1.4` runtime. `runtime: "bun-1.4"` deploys on Bun 1.4.4 in
a Bun-only image with no Node.js binary, and the run controller itself
runs under Bun. `runtime: "bun"` keeps today's behavior (Bun 1.3.3 with
Node.js 20 alongside it); `bun-legacy` is accepted as an explicit
spelling of the same runtime.
Bun 1.4 rejects the `--no-warnings=ExperimentalWarning` flag the worker
was started with, so bun workers now get the bare `--no-warnings` form.
The supervisor, build plugins, and rsc extension recognise every bun
runtime instead of only the plain `bun` value.
Docs cover the runtimes, that the `bun-1.4` image contains no Node.js
binary, and the open Bun 1.4 `node:http2` client regression.
Mono-RevId: 29aae0f8cb56dfb912865e00b72169d26b12aaf7
Adds the `bun-1.4` runtime. `runtime: "bun-1.4"` deploys on Bun 1.4.4 in a Bun-only image with no Node.js binary, and the run controller itself runs under Bun. `runtime: "bun"` is unchanged (Bun 1.3 with Node.js alongside it); `bun-legacy` is accepted as an explicit spelling of the same runtime. On Bun 1.4 the worker no longer crashes at startup on the `--no-warnings=ExperimentalWarning` flag.
Copy file name to clipboardExpand all lines: docs/config/config-file.mdx
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -329,7 +329,7 @@ After each call we restore the few attributes we use to link a span to its run,
329
329
330
330
If you don't set a `runtime`, your tasks run on the current Node.js LTS. Setting `runtime: "node"` does the same thing — see the Node.js versions section below to pin a specific version instead.
331
331
332
-
We currently only officially support the `node` runtime, but you can try our experimental `bun` runtime by setting the `runtime` option in your config file:
332
+
We currently only officially support the `node` runtime, but you can try our experimental Bun runtimes by setting the `runtime` option in your config file:
333
333
334
334
```ts trigger.config.ts
335
335
import { defineConfig } from"@trigger.dev/sdk";
@@ -341,7 +341,7 @@ export default defineConfig({
341
341
});
342
342
```
343
343
344
-
See our [Bun guide](/guides/frameworks/bun) for more information.
344
+
`bun` runs on Bun 1.3 with a Node.js binary alongside it. `bun-1.4` runs on a Bun-only image with no Node.js binary. See our [Bun guide](/guides/frameworks/bun) for the differences.
Copy file name to clipboardExpand all lines: docs/snippets/node-versions.mdx
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,15 +4,16 @@ Trigger.dev runs your deployed tasks on one of these runtimes:
4
4
- Node.js `node-22` — `22.23.4`
5
5
- Node.js `node-24` — `24.22.1`
6
6
- Node.js `node-26` — `26.12.1`
7
-
- Bun `bun` — `1.3.3`
7
+
- Bun `bun` — `1.3.3` with Node.js `20` alongside it (also spelled `bun-legacy`)
8
+
- Bun `bun-1.4` — `1.4.4`, no Node.js binary
8
9
9
10
If you don't set a `runtime`, or you set `runtime: "node"`, your tasks run on the current Node.js LTS. That version moves forward as new LTS releases land, so set an explicit version — for example `runtime: "node-24"` — if you need it to stay fixed.
`The "bun" runtime is currently experimental, and certain features may not work, especially opentelemetry instrumentation of 3rd party packages.`
374
+
`The "${config.runtime}" runtime is currently experimental, and certain features may not work, especially opentelemetry instrumentation of 3rd party packages.`
0 commit comments