ASP.NET Core 3.1 React template live reload is extremely slow

[empz]

A fresh new ASP.NET Core 3.1 React app created with dotnet new react using dotnet SDK 3.1.300 is very slow to live reload.

Start the dotnet application, change something in the client App.js, wait for live reload. It takes almost 10s to perform the reload. This is clearly too much for any decent developer experience.

Windows 10 x64
node v12.14.1
dotnet SDK 3.1.300

Is this expected? Is everybody getting the same slowness or is it something related to my setup?

EDIT
Needless to say that if I just run the react app alone, the live reload takes less than a second.

[mkArtakMSFT]

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

[superdopey]

I have the same experience, I agree that this is a very bad developer experience.

[empz]

Yes, it's unusable. Moved to Next.js.

[superdopey]

I have disabled the spa for now
// if (env.IsDevelopment()) // { // spa.UseReactDevelopmentServer(npmScript: "start"); // }

And I run npm start manually, which is far from ideal but works for now. I did hope for a better reaction from aspnetcore team.

[jjleavitt]

I was able to get hot module refreshes down to 2 seconds by:

1. overriding the CRA config to use Fast-Refresh via packages and instructions here:
   https://github.com/esetnik/customize-cra-react-refresh
2. run development directly on kestrel, without IIS Express

[javiercn]

@empz thanks for contacting us.

We've significantly changed the way the SPA templates are setup for development and production to align with how other backend frameworks approach this and as a result we no longer use SpaServices as part of the development workflow.

While we haven't removed or obsoleted the code, we don't plan to make future changes/fixes on it and we recommend people migrate to the new approach we use in the templates.

We recommend switching to the new approach that leverages the SPA proxy in front of the ASP.NET Core and doesn't have these issues.