SCSS not updating and Fast Refresh issues after macOS update

testBP0612 commented 1 year ago

Verify canary release

[X] I verified that the issue exists in the latest Next.js canary release

Provide environment information

    Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 22.6.0: Wed Jul  5 22:22:05 PDT 2023; root:xnu-8796.141.3~6/RELEASE_ARM64_T6000
    Binaries:
      Node: 16.19.0
      npm: 8.19.3
      Yarn: N/A
      pnpm: N/A
    Relevant packages:
      next: 13.1.6
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0

Which area(s) of Next.js are affected? (leave empty if unsure)

Middleware / Edge (API routes, runtime), Operating System (Windows, MacOS, Linux)

Link to the code that reproduces this issue or a replay of the bug

none

To Reproduce

Update macOS to Ventura 13.5.1
Run next dev in my Next.js project.
Make changes to SCSS files.
Observe that changes are not reflected immediately and Fast Refresh performs a full reload.

Describe the Bug

After updating my macOS, I've been experiencing issues with SCSS not updating immediately and Fast Refresh having to perform a full reload. Everything was working perfectly before the update.

Expected Behavior

SCSS should update immediately and Fast Refresh should work without performing a full reload.

Which browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

testBP0612 commented 1 year ago

I solved it

limegorilla commented 1 year ago

Can also attest to this. macOS 14 Beta 7 (23A5337a)

I'm using TailwindCSS so don't think it's styling related - any changes or route changes will cause the page to hard refresh - my production site doesn't experience the same issue so I am assuming it's server related. Switching between Chrome/Chromium or Safari also doesn't change anything.

Happy to run any diagnostics if required.

YCMitch commented 10 months ago

Every thread here about fast refresh not working with Sass/CSS/Tailwind etc just gets completely ignored.

I'm just kinda getting used to a full refresh after any client component or styling change - feels a bit nostalgic, like working with jQuery on old WordPress sites lol. You're not gonna get a response, unfortunately. This is the future 😅

vercel / next.js