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
Cloning the folder, installing packages, as well as missing @swc/core and @workflow/swc-plugin, and running bun run dev.
Getting the following error:
bun run dev
$ bun x workflow build && PORT=3152 bun run server.ts
Using target: standalone
Building with StandaloneBuilder
Creating steps bundle at ./.well-known/workflow/v1/step.js
Discovering workflow directives 116ms
Created steps bundle 184ms
Creating workflows bundle at ./.well-known/workflow/v1/flow.js
Created intermediate workflow bundle 14ms
Created final workflow bundle 53ms
Creating webhook bundle at ./.well-known/workflow/v1/webhook.js
Creating webhook route
Build completed successfully!
Workflow plugin loaded
error: plugin
× failed to invoke plugin on 'Some("./workflows-bun-adapter/workflows/user-signup.ts")'
code: "GenericFailure"
Quick update, I had to pin "@swc/core": "1.11.24" (saw this in your package lock file) and it's now working. Any plans to support more latest SWC versions, or update the example to include the missing packages in package.json + pin to the supported @swc/core version?
Update: The breaking change on SWC's side probably happened somewhere in 1.13.x or 1.14.x. The 1.12.x seems to work.
Thanks @arielweinberger. Likely not right now since swc version migrations are extremely tricky. Since the compiler works and isn't really a bottleneck, I don't think we'll bump swc core versions anytime soon unless there's a meaningful reason to like a reported security vulnerability
Activity
arielweinberger commentedon Nov 30, 2025
Quick update, I had to pin
"@swc/core": "1.11.24"(saw this in your package lock file) and it's now working. Any plans to support more latest SWC versions, or update the example to include the missing packages in package.json + pin to the supported @swc/core version?Update: The breaking change on SWC's side probably happened somewhere in
1.13.xor1.14.x. The1.12.xseems to work.pranaygp commentedon Dec 5, 2025
Thanks @arielweinberger. Likely not right now since swc version migrations are extremely tricky. Since the compiler works and isn't really a bottleneck, I don't think we'll bump swc core versions anytime soon unless there's a meaningful reason to like a reported security vulnerability
pranaygp commentedon Dec 5, 2025
do we need to pin the swc version in the bun example via bun.lock?