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

Fast Refresh taking longer than 4 seconds #36337

Closed
1 task done
shikev opened this issue Apr 21, 2022 · 2 comments
Closed
1 task done

Fast Refresh taking longer than 4 seconds #36337

shikev opened this issue Apr 21, 2022 · 2 comments
Labels
bug Issue was opened via the bug report template.

Comments

@shikev
Copy link

shikev commented Apr 21, 2022

Verify canary release

  • I verified that the issue exists in Next.js canary release

Provide environment information

Operating System:
Platform: darwin
Arch: x64
Version: Darwin Kernel Version 21.4.0: Fri Mar 18 00:45:05 PDT 2022; root:xnu-8020.101.4~15/RELEASE_X86_64
Binaries:
Node: 16.14.2
npm: 8.5.5
Yarn: 1.22.18
pnpm: N/A
Relevant packages:
next: 12.1.6-canary.4
react: 18.0.0
react-dom: 18.0.0

What browser are you using? (if relevant)

Version 100.0.4896.88 (Official Build) (x86_64)

How are you deploying your application? (if relevant)

(locally)

Describe the Bug

Fast Refresh isn't working as fast as advertised — it's taking roughly four seconds for text edits. Seems remarkably similar to the issue described in this closed issue that @timneutkens worked on earlier. I'm on the canary version and this is still happening.

Additionally — unsure if it's related — when I first run yarn dev and load the homepage it takes ~30 seconds, which feels longer than it I've experienced in the past.

Expected Behavior

Fast refresh is near instantaneous as it was in the past.

To Reproduce

Steps:

  1. Create a Next.js app using npx create-next-app@latest
  2. Run yarn dev
  3. Make edits

image

@shikev shikev added the bug Issue was opened via the bug report template. label Apr 21, 2022
@shikev
Copy link
Author

shikev commented Apr 21, 2022

Never mind, I'm a dunce and left throttling on 😨

@shikev shikev closed this as completed Apr 21, 2022
@github-actions
Copy link
Contributor

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 21, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue was opened via the bug report template.
Projects
None yet
Development

No branches or pull requests

1 participant