Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bun --bun run dev exits silently from 3.7.0 #150

Closed
Eckhardt-D opened this issue Sep 7, 2023 · 4 comments
Closed

bun --bun run dev exits silently from 3.7.0 #150

Eckhardt-D opened this issue Sep 7, 2023 · 4 comments
Labels
bug Something isn't working bun

Comments

@Eckhardt-D
Copy link

Since the introduction of the internal dev server being forked as a child process bun --bun run dev and bunx --bun nuxt dev will exit silently with a zero code.

This happens because child_process.fork() is only partially implemented in Bun. Specifically Bun does not do IPC on child processes yet.

This is an issue in Bun and not Nuxi.

@pi0 pi0 added bug Something isn't working bun labels Sep 7, 2023
@Eckhardt-D
Copy link
Author

oven-sh/bun#4468 The good news is that IPC is being worked on heavily here and looks like it will be released soon.

@paperdave
Copy link

that pr will fix things, so long as you don't do anything too wacky with the stdio option. (cant pass more than 3 params to that array).

@pi0
Copy link
Member

pi0 commented Sep 7, 2023

I will be working on a non-forked mode of dev command to unblock this in meantime. BTW if you try nuxi _dev, there will be other issues we should investigate for bun:

 WARN  nuxi _dev is an internal command and should not be used directly. Please use nuxi dev instead.                                           nuxi 1:04:34 PM

✔ Listening on http://127.0.0.1:64057/                                                                                                         nuxi 1:04:34 PM
ℹ Dev server event: type="nuxt:internal:dev:loading" message="Starting nuxt..."                                                                nuxi 1:04:34 PM
  ➜ WSS:      ws://localhost:8080/ws                                                                                                                 1:04:34 PM

✔ Nitro built in 286 ms                                                                                                                       nitro 1:04:36 PM
ℹ Dev server event: type="nuxt:internal:dev:ready" port=64057                                                                                  nuxi 1:04:36 PM
ℹ Vite client warmed up in 868ms                                                                                                                    1:04:36 PM

 ERROR  [h3] [unhandled] Unable to connect. Is the computer able to access the url?                                                                  1:04:40 PM

  at new H3Error (node_modules/.pnpm/h3@1.8.1/node_modules/h3/dist/index.mjs:45:4)
  at createError (node_modules/.pnpm/h3@1.8.1/node_modules/h3/dist/index.mjs:78:26)
  at <anonymous> (node_modules/.pnpm/h3@1.8.1/node_modules/h3/dist/index.mjs:1842:25)
  at processTicksAndRejections (:1:1302)

@pi0
Copy link
Member

pi0 commented Sep 7, 2023

forked disabling done #153, #154

dev server issue by nitrojs/nitro#1702

@pi0 pi0 closed this as completed Sep 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working bun
Projects
None yet
Development

No branches or pull requests

3 participants