bug: pnpm run dev fails

[sanjeethboddi]

Provide environment information

System: OS: macOS 14.5 CPU: (8) arm64 Apple M2 Memory: 73.63 MB / 16.00 GB Shell: 5.9 - /bin/zsh Binaries: Node: 20.16.0 - ~/.nvm/versions/node/v20.16.0/bin/node Yarn: 1.22.21 - ~/.nvm/versions/node/v18.12.1/bin/yarn npm: 10.8.1 - ~/.nvm/versions/node/v20.16.0/bin/npm pnpm: 9.5.0 - /opt/homebrew/bin/pnpm

Describe the bug

pnpm run dev:next fails

> create-t3-turbo@ dev:next /sd/x
> turbo watch dev -F @acme/nextjs...

turbo 2.0.11

• Packages in scope: @acme/api, @acme/auth, @acme/db, @acme/eslint-config, @acme/nextjs, @acme/prettier-config, @acme/tailwind-config, @acme/tsconfig, @acme/ui, @acme/validators
• Running dev in 10 packages
• Remote caching disabled
  × failed to connect to daemon
  ╰─▶ server is unavailable: channel closed

 ELIFECYCLE  Command failed with exit code 1.

Link to reproduction

https://github.com/t3-oss/create-t3-turbo

To reproduce

just clone and run

Additional information

No response

[sanjeethboddi]

[juliusmarminge]

Try pnpm turbo daemon restart

[dBianchii]

I reported this same issue here:

https://github.com/vercel/turbo/issues/8491

For now, I need to run turbo daemon clean every once in a while and try running the command again 2 times

[sanjeethboddi]

I reported this same issue here:

vercel/turbo#8491

For now, I need to run turbo daemon clean every once in a while and try running the command again 2 times

After doing turbo daemon clean I'm getting this error discovery failed: bad grpc status code: The operation was cancelled

will track the status of vercel/turbo/issues/8491

[sanjeethboddi]

@dBianchii Could you please suggest other ways to get the template up and running without using turbo?

[dBianchii]

@dBianchii Could you please suggest other ways to get the template up and running without using turbo?

I only use it with turbo. You can also go to apps/NextJS and run pnpm dev which should also work

[juliusmarminge]

Would you please mind checking if upgrading to latest turbo (part of #1144) fixes your issue?

Run pnpm turbo daemon restart too after upgrading for good measure

[sanjeethboddi]

@juliusmarminge No it doesn't fix the issue.

[dBianchii]

Has anyone found a solution? It's so annoying having to restart the daemon every time

[Shashivadan]

After executing the command pnpm turbo daemon restart and including the discord authentication variables in the .env file, the process worked successfully for me.

[techwithanirudh]

Yeah, I'm having the same issue here while using t3-turbo. I'm on the latest version of Turborepo.

[parteekmalik]

is someone found a solution for this?

[flyingwebie]

is someone found a solution for this?

I had the same issue and here is my provide environment information

System:

OS: macOS Tahoe 26.2 CPU: Apple M4 Memory: 24.00 GB Shell: /bin/zsh

Binaries:

Node: 22.21.0 npm: 10.9.4 pnpm: 10.19.0 turbo: 2.5.8

This is the solution that worked for me.

Edit your package.json in the root folder

Before linee 16 and 17

    "dev": "turbo watch dev --continue",
    "dev:next": "turbo watch dev -F @acme/nextjs...",

After linee 16 and 17

    "dev": "turbo dev --continue",
    "dev:next": "turbo dev -F @acme/nextjs...",

Removing watch fixed the problem for me.