Fast Refresh is not working

[oceandrama]

What is the problem?

Fast Refresh during development is not working. It's necessary to manual refresh the page to see new version

What are detailed steps to reproduce this?

1. npm install -g blitz@latest
2. blitz new app (select TypeScript, Full and react-hook-form)
3. cd app
4. blitz dev
5. change the source code

Run blitz -v and paste the output here:

Blitz version: 2.0.0-beta.3 (global)
Blitz version: 2.0.0-beta.3 (local)
Windows 11 | win32-x64 | Node: v16.14.2


 Package manager: npm

  System:
    OS: Windows 10 10.0.22000
    CPU: (6) x64 Intel(R) Core(TM) i5-9400 CPU @ 2.90GHz
    Memory: 6.59 GB / 15.84 GB
  Binaries:
    Node: 16.14.2 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.15 - C:\Program Files\nodejs\yarn.CMD
    npm: 8.5.0 - C:\Program Files\nodejs\npm.CMD
  npmPackages:
    @blitzjs/auth: 2.0.0-beta.3 => 2.0.0-beta.3
    @blitzjs/next: 2.0.0-beta.3 => 2.0.0-beta.3
    @blitzjs/rpc: 2.0.0-beta.3 => 2.0.0-beta.3
    @prisma/client: 4.0.0 => 4.0.0
    blitz: 2.0.0-beta.3 => 2.0.0-beta.3
    next: 12.2.5 => 12.2.5
    prisma: 4.0.0 => 4.0.0
    react: 18.2.0 => 18.2.0
    react-dom: 18.2.0 => 18.2.0
    typescript: ^4.5.3 => 4.8.3

[itsdillon]

Can you share a little more context?

I notice you're using windows. So I'm wondering if it's happening with a fresh blitz install on windows?

[oceandrama]

What do you mean "fresh install"? I've had already installed global version of blitz v1 and update it to v2 before run blitz new But after creating new project it's using a local version of blitz, which is absolutely "fresh", isn't it?

[itsdillon]

I see. So you're getting the issue with the default index page that blitz generates for you?

I ask, because I haven't had an issue running on osx

[beerose]

Closing due to inactivity.