-
Notifications
You must be signed in to change notification settings - Fork 26.3k
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
next.js >= 14.0.5-canary.59 Fast Refresh had to perform a full reload #65974
Comments
We cannot recreate the issue with the provided information. Please add a reproduction in order for us to be able to investigate. Why was this issue marked with the
|
I met the same problem, that it tends to have unnecessary full reload in development, even when I just changed a dumb component. I am using Next14.2.3. |
This issue has been automatically closed because it received no activity for a month and had no reproduction to investigate. If you think it was closed by accident, please leave a comment. If you are running into a similar issue, please open a new issue with a reproduction. Thank you. |
This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you. |
Link to the code that reproduces this issue
https://github.com/gdccwxx/reproduction-app
To Reproduce
Current vs. Expected behavior
current:
![image](https://private-user-images.githubusercontent.com/28426137/332021825-8e3a8736-3c1d-4732-a4e4-41b2fb9e6c91.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjE5NzExNTMsIm5iZiI6MTcyMTk3MDg1MywicGF0aCI6Ii8yODQyNjEzNy8zMzIwMjE4MjUtOGUzYTg3MzYtM2MxZC00NzMyLWE0ZTQtNDFiMmZiOWU2YzkxLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MjYlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzI2VDA1MTQxM1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWQxNTQ4ZGFiNDA2NmE1MTIwNTBhMDVhMWJjYWMwNDBlNTllODZmNmRiYmRlYjc5MzAxZWVmOGUwYTcyMWVkMDQmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.hArxKt5ie5hk9Ys7MISv-feqOS6sRXFgf4bzOCO3BW4)
expected:
![image](https://private-user-images.githubusercontent.com/28426137/332021854-ebd4c326-5146-4074-bd6e-28f119b64857.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjE5NzExNTMsIm5iZiI6MTcyMTk3MDg1MywicGF0aCI6Ii8yODQyNjEzNy8zMzIwMjE4NTQtZWJkNGMzMjYtNTE0Ni00MDc0LWJkNmUtMjhmMTE5YjY0ODU3LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MjYlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzI2VDA1MTQxM1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTJiOTM1YmFlZTRjZmI4NjUzMjI5NmJkZjhmNGJmZGY5YWRkN2EzZDBmNmYxZjMyOGZiYTVkMmZjYWQ0ZWE5OWImWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.SNnednGCs4Q_wWkpfdOrvqIWLHrgZ_9z7GSNBD55dgY)
Provide environment information
Operating System: Platform: darwin Arch: arm64 Version: Darwin Kernel Version 23.4.0: Fri Mar 15 00:10:42 PDT 2024; root:xnu-10063.101.17~1/RELEASE_ARM64_T6000 Binaries: Node: 18.19.0 npm: 10.2.3 Yarn: 1.22.10 pnpm: N/A Relevant Packages: next: 14.0.5-canary.59 eslint-config-next: 14.2.3 react: 18.3.1 react-dom: 18.3.1 typescript: 4.6.2 Next.js Config: output: standalone
Which area(s) are affected? (Select all that apply)
Metadata, Output (export/standalone), Turbopack
Which stage(s) are affected? (Select all that apply)
next dev (local)
Additional context
npm run dev when metadata.assetQueryString is empty && not safari && not chrome
i know the reason cause the problem, but I don't know the history of that code.please to fix it~ @sokra
The text was updated successfully, but these errors were encountered: