Closed Jarred-Sumner closed 5 months ago
cc @timneutkens @leerob
Congrats to the Bun team on shipping this! :)
Note that that running bun --bun next dev
still errors for apps using middleware, blocked on #5648 (see #9447)
Congrats to the Bun team on shipping this! :)
Note that that running
bun --bun next dev
still errors for apps using middleware, blocked on #5648 (see #9447)
Indeed been trying to push this issue for months because otherwise bun is not production ready to work with under nextjs14
Anyone else seeing high CPU usage when running the next dev server with bun --bun next dev
? This is refreshing the page a few times:
Anyone else seeing high CPU usage when running the next dev server with
bun --bun next dev
? This is refreshing the page a few times:
Personally I can't even run it because am I using nextjs 14 middleware
Known major blockers:
undici
override (instead of a prebundled version) in Bunws
override (instead of a prebundled version) in BunThe first issue is here:
Bun has a builtin polyfill for "undici" which uses the globals for
fetch
,Request
, etc instead of a JS implementation. When run in Bun, next should use that. The same for"ws"
.