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

bug: nextjs crashes after file changes when running pnpm run dev #1240

Open
tconroy opened this issue Nov 4, 2024 · 4 comments
Open

bug: nextjs crashes after file changes when running pnpm run dev #1240

tconroy opened this issue Nov 4, 2024 · 4 comments

Comments

@tconroy
Copy link

tconroy commented Nov 4, 2024

Provide environment information

System:
OS: macOS 15.0.1
CPU: (10) arm64 Apple M1 Max
Memory: 4.28 GB / 64.00 GB
Shell: 5.9 - /opt/homebrew/bin/zsh
Binaries:
Node: 20.16.0 - ~/.local/state/fnm_multishells/56907_1730686687697/bin/node
Yarn: 1.22.22 - /opt/homebrew/bin/yarn
npm: 10.8.1 - ~/.local/state/fnm_multishells/56907_1730686687697/bin/npm
pnpm: 9.12.3 - ~/.local/state/fnm_multishells/56907_1730686687697/bin/pnpm
bun: 1.1.34 - /opt/homebrew/bin/bun
Watchman: 2024.10.28.00 - /opt/homebrew/bin/watchman

Describe the bug

live reload for nextjs is not working, and appears to be silently crashing the nextjs server on code changes.

Link to reproduction

NA

To reproduce

after running pnpm run dev from the repo root, nextjs boots and I can view the app. However, as soon as I make an edit to a file (such as changing some text or adding a new route), the page does not update. If I refresh the page manually, I get ERR_CONNECTION_REFUSED in the browser.

Additional information

There is no error output in the terminal.

Interestingly, if I cd into apps/next and pnpm run dev the app directly, it works correctly.

This specifically seems to be a turbo-related issue.

@OopsOverflow
Copy link

I had the same bug. I rolledback this change #1227 locally and it stopped happening on my machine, others on windows still experience the same issue.
Which Next.js version are you using btw?

@juliusmarminge
Copy link
Member

Do you have this set in the nextjs turbo config? https://github.com/t3-oss/create-t3-turbo/blob/main/apps/nextjs/turbo.json#L10

@OopsOverflow
Copy link

Do you have this set in the nextjs turbo config? https://github.com/t3-oss/create-t3-turbo/blob/main/apps/nextjs/turbo.json#L10

Yes I can confirm that the problem persists even with this (project default) config.

@OopsOverflow
Copy link

Looks like the same behaviour as this.
Upgrading to 2.2.4-canary.9 fixes the issue for the moment. Waiting for the stable release 🤞🏻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants