WSL 2: ReactJS not reloading after saved. [Solved] #10253

PrajjwalDatir · 2020-12-16T09:33:38Z

Is your proposal related to a problem?

WSL2 : ReactJS not reloading after saved.

I recently installed WSL 2 but when I create an app using create-react-app and use npm start the app was’t reloaded when I edited and saved some file

Describe the solution you'd like

I want to use Hot Reloading on my Projects located in Windows file system.

WSL2 changed the file sharing protocol, from using their own custom developed protocol using the 9P protocol, which does not support file changes event for Create React App.

Describe alternatives you've considered

To FIX this issue : You can put your code on the Linux file system (example : in your user’s home directory ), and access these files through the WSL share, \wsl$\DISTRO_NAME from Windows.

Additional context

I wrote everything properly again here

https://prajjwaldatir.medium.com/create-react-app-not-working-62fc9fc4368b

bennettdams · 2020-12-17T16:04:38Z

Did you try it out with the CHOKIDAR_USEPOLLING environment variable?

PrajjwalDatir · 2020-12-18T09:16:09Z

@bennettdams CHOKIDAR_USEPOLLING is if I'm running my react app inside a VM right!?

I tried all other troubleshooting methods, none of them worked.

I'm not running my project inside VM so why & how do I use CHOKIDAR_USEPOLLING=true ?

bennettdams · 2020-12-18T09:27:42Z

@PrajjwalDatir "VM" is just the example the CRA team used for their documentation there. Really, Chokidar is a file watcher for Node, so it handles the "proxy" part of your development setup (remote container, WSL, VM, etc.).
How do I know? Just last week I set up a project with VS Code's Remote Containers, which had exactly the same problem you described here. With Chokidar, my changes are actually noticed by VS Code.

To quickly test it out, just change your start script in the package.json to
{ ... "start": "CHOKIDAR_USEPOLLING=true react-scripts start" ... }

PrajjwalDatir · 2020-12-19T07:21:44Z

Thanks! It works now 🕺
#10197 is the parent issue of this, so I'm closing this issue.

For future readers,
Inside your package.json

find

"scripts": {
    "start": "react-scripts start",
    "build": "react-scripts build",
    "test": "react-scripts test",
    "eject": "react-scripts eject"
  }

and replace it with

"scripts": {
    "start": "CHOKIDAR_USEPOLLING=true react-scripts start",
    "build": "react-scripts build",
    "test": "react-scripts test",
    "eject": "react-scripts eject"
  }

I'm developing on the Windows subsystem for Linux, and the dev server wasn't auto-reloading when I made changes to the site. Followed the advice here to get a fix: facebook/create-react-app#10253

vivek-settlemint · 2021-10-12T04:44:27Z

I moved my code from the mounted file system to ubuntu file system in ~/home and it worked!

resyfer · 2021-10-13T11:41:18Z

I believe this issue happens for stuff that use the Chokidar package... React, Vue, Nodemon....all don't reload on save

nurshom · 2021-12-29T18:30:55Z

Thanks! It works now 🕺 #10197 is the parent issue of this, so I'm closing this issue.

For future readers, Inside your package.json
"scripts": {
    "start": "CHOKIDAR_USEPOLLING=true react-scripts start",
  }

This didn't solve the issue for me. My situation remains same as described in the original issue description.

I have also tried the CHOKIDAR_USEPOLLING=true in a .env file (technically the same thing as this solution) to no effect.

sushmitg · 2021-12-31T09:56:52Z

Thanks! It works now 🕺 #10197 is the parent issue of this, so I'm closing this issue.
For future readers, Inside your package.json
"scripts": {
    "start": "CHOKIDAR_USEPOLLING=true react-scripts start",
  }
This didn't solve the issue for me. My situation remains same as described in the original issue description.

I have also tried the CHOKIDAR_USEPOLLING=true in a .env file (technically the same thing as this solution) to no effect.

I am facing the Same Issue.

archit11111 · 2022-01-02T17:49:04Z

Thanks! It works now 🕺 #10197 is the parent issue of this, so I'm closing this issue.
For future readers, Inside your package.json
"scripts": {
    "start": "CHOKIDAR_USEPOLLING=true react-scripts start",
  }
This didn't solve the issue for me. My situation remains same as described in the original issue description.
I have also tried the CHOKIDAR_USEPOLLING=true in a .env file (technically the same thing as this solution) to no effect.
I am facing the Same Issue.

Same Issue here as well. Are you on Windows 11?

sushmitg · 2022-01-03T07:34:58Z

Thanks! It works now 🕺 #10197 is the parent issue of this, so I'm closing this issue.
For future readers, Inside your package.json
"scripts": {
    "start": "CHOKIDAR_USEPOLLING=true react-scripts start",
  }
This didn't solve the issue for me. My situation remains same as described in the original issue description.
I have also tried the CHOKIDAR_USEPOLLING=true in a .env file (technically the same thing as this solution) to no effect.
I am facing the Same Issue.
Same Issue here as well. Are you on Windows 11?

Yes I am. My projects folder was placed on Desktop means in C: drive after some research I found out I need to place the project in linux folder itself. So I moved the project to linux folder i.e., "wsl\Ubuntu\home{$username}" and it worked even without CHOKIDAR_USEPOLLING=true . hope it helps.

archit11111 · 2022-01-03T15:08:22Z

Thanks! It works now 🕺 #10197 is the parent issue of this, so I'm closing this issue.
For future readers, Inside your package.json
"scripts": {
    "start": "CHOKIDAR_USEPOLLING=true react-scripts start",
  }
This didn't solve the issue for me. My situation remains same as described in the original issue description.
I have also tried the CHOKIDAR_USEPOLLING=true in a .env file (technically the same thing as this solution) to no effect.
I am facing the Same Issue.
Same Issue here as well. Are you on Windows 11?
Yes I am. My projects folder was placed on Desktop means in C: drive after some research I found out I need to place the project in linux folder itself. So I moved the project to linux folder i.e., "wsl\Ubuntu\home{$username}" and it worked even without CHOKIDAR_USEPOLLING=true . hope it helps.

Thanks! But I think it should have worked just using CHOKIDAR_USEPOLLING=true as many have said this solves the issue. But as pointed out here - https://stackoverflow.com/questions/69759267/docker-not-detecting-changes-for-react-app-in-windows, maybe this issue might be specific to windows 11

nurshom · 2022-01-10T17:36:59Z

Thanks! But I think it should have worked just using CHOKIDAR_USEPOLLING=true as many have said this solves the issue. But as pointed out here - https://stackoverflow.com/questions/69759267/docker-not-detecting-changes-for-react-app-in-windows, maybe this issue might be specific to windows 11

I am using Windows 10 with WSL2/Ubuntu 20.04 and experiencing the same issue. So it might not be specific to W11. As we see from others' comments, using CHOKIDAR_USEPOLLING=true should have fixed it but it hasn't for us. Which tells me the issue may have a different origin for some of the cases.

KolyanLock · 2022-01-26T13:20:32Z

Thanks! It works now 🕺 #10197 is the parent issue of this, so I'm closing this issue.

For future readers, Inside your package.json

find
"scripts": {
    "start": "react-scripts start",
    "build": "react-scripts build",
    "test": "react-scripts test",
    "eject": "react-scripts eject"
  }
and replace it with
"scripts": {
    "start": "CHOKIDAR_USEPOLLING=true react-scripts start",
    "build": "react-scripts build",
    "test": "react-scripts test",
    "eject": "react-scripts eject"
  }

Does not work :(

ianisms · 2022-01-26T19:58:58Z

+1 none of the proposed solutions are working for me on Win 11 WSL, node v17.4.0, npm v8.3.2, create-react-app v5.0.0, react v17.0.2

chadlyalan · 2022-02-10T19:19:58Z

Thanks! It works now 🕺 #10197 is the parent issue of this, so I'm closing this issue.
For future readers, Inside your package.json
"scripts": {
    "start": "CHOKIDAR_USEPOLLING=true react-scripts start",
  }
This didn't solve the issue for me. My situation remains same as described in the original issue description.
I have also tried the CHOKIDAR_USEPOLLING=true in a .env file (technically the same thing as this solution) to no effect.
I am facing the Same Issue.
Same Issue here as well. Are you on Windows 11?
Yes I am. My projects folder was placed on Desktop means in C: drive after some research I found out I need to place the project in linux folder itself. So I moved the project to linux folder i.e., "wsl\Ubuntu\home{$username}" and it worked even without CHOKIDAR_USEPOLLING=true . hope it helps.

This is what I had to do to get it working again for me. Nothing else was working. Thanks for the advice.

MubashirullahD · 2022-03-08T09:10:11Z

Can confirm for Windows 11 with WSL2; having a react project; that the Chokidar thing works. Once I added it, I did npm start again. Adding changes and then saving automatically brings the changes. Relatively faster than restarting the whole thing. Many thanks.

Workata · 2022-03-11T14:00:28Z

I had the same problem with hot reload on WSL even after changing package.json ("start": "CHOKIDAR_USEPOLLING=true react-scripts start").

After changing react-scripts version (and then npm install) hot reload works again.

"dependencies": {
//...
"react-scripts": "4.0.3", // previously I had 5.0.0
//...
}

Bizzle-Dapp · 2022-03-11T21:51:29Z

Good evening everyone,
Tonight I bring you an alternative to the madness.

If running Win10/Win11 and running Ubuntu WSL2, you will find that the Windows file system has a specific file directory that acts as this VM.

Open file explorer and you can navigate to this directory with \\wsl$ in the search.

You will notice this directory has a folder titled the Ubuntu you are running. Within this folder will be a /mnt directory. Inside, once more, is ./wsl.

This is the folder you should run your project from.

Copy the contents of your project here, open it with your IDE to verify you have permission to do so.

Once it's open, you will need to recursively update permissions on the folder to ensure you have privilege to run your react scripts start command using npm run start.

To do this:
Open Powershell with elevated privilege on your local system. Run your Ubuntu exe. For me it was:

Navigate to the wsl directory, example:

Run this command to update rights, recursively on the directory:
sudo chmod -R +x ./<YourProjectName>
You'll be asked to authenticate, do as the computer asks 👌

Presto.

docker-compose up your project from VSCode or where ever you are deving. If your docker-compose.yml is configured with the correct chokidar_usepolling environment variable, you're good to go.

Hope this helps us Windows users.

Aestersa · 2022-03-14T11:34:24Z

Good evening everyone, Tonight I bring you an alternative to the madness.

If running Win10/Win11 and running Ubuntu WSL2, you will find that the Windows file system has a specific file directory that acts as this VM.

Open file explorer and you can navigate to this directory with \\wsl$ in the search.

You will notice this directory has a folder titled the Ubuntu you are running. Within this folder will be a /mnt directory. Inside, once more, is ./wsl.

This is the folder you should run your project from.

Copy the contents of your project here, open it with your IDE to verify you have permission to do so.

Once it's open, you will need to recursively update permissions on the folder to ensure you have privilege to run your react scripts start command using npm run start.

To do this: Open Powershell with elevated privilege on your local system. Run your Ubuntu exe. For me it was:

Navigate to the wsl directory, example:

Run this command to update rights, recursively on the directory: sudo chmod -R +x ./<YourProjectName> You'll be asked to authenticate, do as the computer asks 👌

Presto.

docker-compose up your project from VSCode or where ever you are deving. If your docker-compose.yml is configured with the correct chokidar_usepolling environment variable, you're good to go.

Hope this helps us Windows users.

This helped for me on Windows 11, Thank you so much!
But i also needed to create project again to run server.

romainiac · 2022-03-16T00:45:56Z

I had the same problem with hot reload on WSL even after changing package.json ("start": "CHOKIDAR_USEPOLLING=true react-scripts start").

After changing react-scripts version (and then npm install) hot reload works again.

"dependencies": { //... "react-scripts": "4.0.3", // previously I had 5.0.0 //... }

I have been debugging for 4 hours, downgrading rom 5.0 5o 4.0.3 solved the problem. I cant thank you enough. I am 4 whiskeys in pulling my hair.

audryhsu · 2022-03-17T18:48:40Z

I had the same problem with hot reload on WSL even after changing package.json ("start": "CHOKIDAR_USEPOLLING=true react-scripts start").

After changing react-scripts version (and then npm install) hot reload works again.

"dependencies": { //... "react-scripts": "4.0.3", // previously I had 5.0.0 //... }

This is what ultimately solved it for me, after trying trying both CHOKIDAR_USEPOLLING=true and FAST_REFRESH=false.

iiian · 2022-04-24T08:57:49Z

Good evening everyone, Tonight I bring you an alternative to the madness.

If running Win10/Win11 and running Ubuntu WSL2, you will find that the Windows file system has a specific file directory that acts as this VM.

...

I am now personally extremely skeptical of this appproach. Would-be adherents beware. Twice now upon resetting my computer, it's completely blown away the directory I put in /mnt/wsl/. The first time I didn't quite realize it, because I used File Explorer to copy files from my Documents folder. The second time I just did a git clone to instantiate the files. I just restarted my machine and now the git clone is gone along with all of my work. 👎

-- edit --
could be a "me" problem, I didn't run chmod -R +x. But still, that seems like a dumb thing to have to do, esp when Ubuntu gives you a /home/user_name directory to work with. Additionally, I'm no linux expert, the only chmodding I ever do is to make scripts executable. If you're like me, be careful.

-- edit 2 --
The chmod didn't help. Long live /home/user_name.

$ cd /mnt/wsl
$ mkdir was_it_my_fault
$ chmod -R +x ./was_it_my_fault

# restarts machine

$ cd /mnt/wsl
$ ls -la
/mnt/wsl > la  
total 0
drwxr-xr-x 4 root root 100 Apr 24 02:03 docker-desktop
drwxr-xr-x 3 root root  60 Apr 24 02:03 docker-desktop-bind-mounts
drwxr-xr-x 6 root root 120 Apr 24 02:03 docker-desktop-data
# guess not maybe

nathanpovo · 2022-05-16T07:48:08Z

Version 5.x.x of react-scripts does not work with CHOKIDAR_USEPOLLING because there was a breaking change in webpack and that variable is no longer supported. The newly added variable WATCHPACK_POLLING has to be used instead.

Inside your package.json find

"scripts": {
    "start": "react-scripts start",

and replace it with

"scripts": {
    "start": "WATCHPACK_POLLING=true react-scripts start",

See #12397 for more info

bhat-anusha · 2022-05-16T16:27:37Z

The reason that version 5.x.x of react-scripts does not work with CHOKIDAR_USEPOLLING is because there was a breaking change in webpack and that variable is no longer supported. The new variable WATCHPACK_POLLING has to be used instead.

Inside your package.json find
"scripts": {
    "start": "react-scripts start",
and replace it with
"scripts": {
    "start": "WATCHPACK_POLLING=true react-scripts start",
See #12397 for more info

This worked for me, thank you very much :)

RohanVDeshpande · 2022-05-17T05:08:41Z

Good evening everyone, Tonight I bring you an alternative to the madness.
If running Win10/Win11 and running Ubuntu WSL2, you will find that the Windows file system has a specific file directory that acts as this VM.
...

I am now personally extremely skeptical of this appproach. Would-be adherents beware. Twice now upon resetting my computer, it's completely blown away the directory I put in /mnt/wsl/. The first time I didn't quite realize it, because I used File Explorer to copy files from my Documents folder. The second time I just did a git clone to instantiate the files. I just restarted my machine and now the git clone is gone along with all of my work. 👎

-- edit -- could be a "me" problem, I didn't run chmod -R +x. But still, that seems like a dumb thing to have to do, esp when Ubuntu gives you a /home/user_name directory to work with. Additionally, I'm no linux expert, the only chmodding I ever do is to make scripts executable. If you're like me, be careful.

-- edit 2 -- The chmod didn't help. Long live /home/user_name.
$ cd /mnt/wsl
$ mkdir was_it_my_fault
$ chmod -R +x ./was_it_my_fault

# restarts machine

$ cd /mnt/wsl
$ ls -la
/mnt/wsl > la  
total 0
drwxr-xr-x 4 root root 100 Apr 24 02:03 docker-desktop
drwxr-xr-x 3 root root  60 Apr 24 02:03 docker-desktop-bind-mounts
drwxr-xr-x 6 root root 120 Apr 24 02:03 docker-desktop-data
# guess not maybe

Agree -- I don't think is the best approach. According to this post, /mnt/wsl is mounted as tmpfs so it will get wiped everytime you restart your computer. You probably shouldn't be using this directory long-term for development.

RohanVDeshpande · 2022-05-17T05:15:31Z

Also, see #10253 (comment) for a solution that worked for me.
Adding WATCHPACK_POLLING=true worked while modifying CHOKIDAR_USEPOLLING and FAST_REFRESH flags (like previous comments suggested) did not.

hubologist24 · 2022-05-17T13:40:45Z

WATCHPACK_POLLING=true works thanks

rehlucena88 · 2022-05-24T16:45:50Z

"scripts": {

Fiz isso e deu certo no meu tbm

michalbidzinski1 · 2022-06-02T11:55:21Z

Although WATCHPACK_POLLING=true works, i still have to refresh the page to see the results. Any ideas?
Im running my react + backend on docker with nginx and docker-compose btw.

vishnupeas · 2022-06-19T08:38:12Z

Version 5.x.x of react-scripts does not work with CHOKIDAR_USEPOLLING because there was a breaking change in webpack and that variable is no longer supported. The newly added variable WATCHPACK_POLLING has to be used instead.

Inside your package.json find
"scripts": {
    "start": "react-scripts start",
and replace it with
"scripts": {
    "start": "WATCHPACK_POLLING=true react-scripts start",
See #12397 for more info

this worked for me, last time hot reload stopped working, the fix for me was reinstalling WSL ubuntu.

87prashant · 2022-06-23T10:21:55Z

@nathanpovo thanks!! you are a life saver, I was finding solution for weeks.
Worked with WSL2.

87prashant · 2022-06-23T10:31:50Z

@michalbidzinski1

Although WATCHPACK_POLLING=true works, i still have to refresh the page to see the results. Any ideas? Im running my react + backend on docker with nginx and docker-compose btw.

What I am experiencing is that refreshing on changes takes a little longer (about 3-5 sec).
Could you check if that's the case with you?

adityavartak07 · 2022-06-26T14:40:27Z

I had the same problem with hot reload on WSL even after changing package.json ("start": "CHOKIDAR_USEPOLLING=true react-scripts start").

After changing react-scripts version (and then npm install) hot reload works again.

"dependencies": { //... "react-scripts": "4.0.3", // previously I had 5.0.0 //... }

Dude man was searching for a solution, since 4 hrs, finally this worked. Thanks man.

lucaszarza · 2022-07-16T20:45:31Z

CHOKIDAR_USEPOLLING=true

I had the same problem with hot reaload on WSL, after using the "CHOKIDAR_USEPOLLING=true" on package-json:

"dev": "CHOKIDAR_USEPOLLING=true vue-cli-service serve",

It Works, althought it's taking a lot of time to show the changes on screen.

P.S. I'm using vue

but thanks anyway!

danielcaze · 2022-08-03T15:11:10Z

I moved my code from the mounted file system to ubuntu file system in ~/home and it worked!

how do I do this?

87prashant · 2022-08-03T15:29:44Z

@danielcaze
Not sure about that, but you can try this: #10253 (comment)
It worked for me👍

ianpegg · 2022-09-26T18:40:14Z

"start": "WATCHPACK_POLLING=true react-scripts start",

After a couple of hours of headscratching this solved the issue for me in my Homestead VM. Thank you!

HuyyNguyenz · 2022-09-29T09:25:08Z

Version 5.x.x of react-scripts does not work with CHOKIDAR_USEPOLLING because there was a breaking change in webpack and that variable is no longer supported. The newly added variable WATCHPACK_POLLING has to be used instead.

Inside your package.json find
"scripts": {
    "start": "react-scripts start",
and replace it with
"scripts": {
    "start": "WATCHPACK_POLLING=true react-scripts start",
See #12397 for more info

Thank you so much, it's finally working again ^^

jerlam06 · 2022-10-27T06:55:46Z

What worked the best for me was to reinstall react-scripts, I first tried to replace the latest version with the 4.0.3, it worked, then I tried the latest (5.0.1) again and it also worked. However, make sure to MANUALLY trigger the first refresh of your app after reinstalling react-scripts, otherwise the auto refresh will not work.

hoa-nguyen-bk · 2022-11-21T16:45:26Z

due to some answer in stackoverflow, that I'm so sorry for forgetting who answered that, I could fix this bug because I set up my wsl from version 2 to version 1.
Here is my command in Powershell (with administrator, absolutely)

wsl --set-version ubuntu 1

olsonperrensen · 2022-12-07T14:56:26Z

Version 5.x.x of react-scripts does not work with CHOKIDAR_USEPOLLING because there was a breaking change in webpack and that variable is no longer supported. The newly added variable WATCHPACK_POLLING has to be used instead.

Inside your package.json find
"scripts": {
    "start": "react-scripts start",
and replace it with
"scripts": {
    "start": "WATCHPACK_POLLING=true react-scripts start",
See #12397 for more info

Thank you! Working now.

Edit: Docker Toolbox also supported!

Reference: facebook/create-react-app#10253

gaurpulkit · 2023-03-15T16:41:01Z

Version 5.x.x of react-scripts does not work with CHOKIDAR_USEPOLLING because there was a breaking change in webpack and that variable is no longer supported. The newly added variable WATCHPACK_POLLING has to be used instead.

Inside your package.json find
"scripts": {
    "start": "react-scripts start",
and replace it with
"scripts": {
    "start": "WATCHPACK_POLLING=true react-scripts start",
See #12397 for more info

If anyone is using WSL 2 and react-scripts, then THIS IS THE WAY!

facebook/create-react-app#10253 (comment)

independenceee · 2023-07-04T13:16:05Z

Is your proposal related to a problem?

WSL2 : ReactJS not reloading after saved.

I recently installed WSL 2 but when I create an app using create-react-app and use npm start the app was’t reloaded when I edited and saved some file

Describe the solution you'd like

I want to use Hot Reloading on my Projects located in Windows file system.

WSL2 changed the file sharing protocol, from using their own custom developed protocol using the 9P protocol, which does not support file changes event for Create React App.

Describe alternatives you've considered

To FIX this issue : You can put your code on the Linux file system (example : in your user’s home directory ), and access these files through the WSL share, \wsl$\DISTRO_NAME from Windows.

Additional context

I wrote everything properly again here

https://prajjwaldatir.medium.com/create-react-app-not-working-62fc9fc4368b

WATCHPACK_POLLING=true in .env files

GabrielFMPinheiro · 2024-01-23T02:21:00Z

Version 5.x.x of react-scripts does not work with CHOKIDAR_USEPOLLING because there was a breaking change in webpack and that variable is no longer supported. The newly added variable WATCHPACK_POLLING has to be used instead.

Inside your package.json find
"scripts": {
    "start": "react-scripts start",
and replace it with
"scripts": {
    "start": "WATCHPACK_POLLING=true react-scripts start",
See #12397 for more info

Thx so much! This worked using colima on Mac

PrajjwalDatir added issue: proposal needs triage labels Dec 16, 2020

PrajjwalDatir closed this as completed Dec 19, 2020

PrajjwalDatir mentioned this issue Dec 19, 2020

[v4.0.1] Environment variable CHOKIDAR_USEPOLLING only works without the "REACT_APP_" prefix #10197

Closed

PrajjwalDatir changed the title ~~WSL 2: ReactJS not reloading after saved.~~ WSL 2: ReactJS not reloading after saved. [Solved] Dec 19, 2020

PrajjwalDatir mentioned this issue Jan 4, 2021

Create React App Not Working? WSL2 - [workaround avaliable] #10254

Closed

chloesun mentioned this issue Jan 12, 2021

HRM not working on WSL 2 microsoft/WSL#4417

Closed

ghominejad mentioned this issue Jan 30, 2022

CHOKIDAR_USEPOLLING doesn't work on docker and Windows 11 #12002

Open

danielcaze mentioned this issue Aug 3, 2022

how can i do this? #12633

Closed

KennethTrecy added a commit to KennethTrecy/docker_mocha that referenced this issue Dec 22, 2022

chore: add missing environment variable to watch properly

705d890

Reference: facebook/create-react-app#10253

Winand added a commit to Winand/realtime-chat-go-react that referenced this issue Apr 2, 2023

[frontend] Fix: auto reload

57a5651

facebook/create-react-app#10253 (comment)

JapuDCret mentioned this issue Dec 2, 2023

Not working with WSL2 arnoson/vite-plugin-live-reload#10

Closed

Matsuuu mentioned this issue Jan 20, 2024

feat: Add option to modify chokidar watchOptions with @web/dev-server modernweb-dev/web#2614

Merged

faradox mentioned this issue Mar 7, 2024

Hot reload / rebuild not working on make run-dev okio-ai/nendo-platform#45

Closed

HalkScout mentioned this issue Aug 31, 2024

[Question] Frontend development, how to hot reload? cvat-ai/cvat#8368

Closed

WSL 2: ReactJS not reloading after saved. [Solved] #10253

WSL 2: ReactJS not reloading after saved. [Solved] #10253

Comments

PrajjwalDatir commented Dec 16, 2020

Is your proposal related to a problem?

Describe the solution you'd like

Describe alternatives you've considered

Additional context

bennettdams commented Dec 17, 2020

PrajjwalDatir commented Dec 18, 2020

bennettdams commented Dec 18, 2020 • edited Loading

PrajjwalDatir commented Dec 19, 2020 • edited Loading

vivek-settlemint commented Oct 12, 2021

resyfer commented Oct 13, 2021

nurshom commented Dec 29, 2021 • edited Loading

sushmitg commented Dec 31, 2021

archit11111 commented Jan 2, 2022

sushmitg commented Jan 3, 2022

archit11111 commented Jan 3, 2022

nurshom commented Jan 10, 2022

KolyanLock commented Jan 26, 2022

ianisms commented Jan 26, 2022 • edited Loading

chadlyalan commented Feb 10, 2022

MubashirullahD commented Mar 8, 2022

Workata commented Mar 11, 2022

Bizzle-Dapp commented Mar 11, 2022 • edited Loading

Aestersa commented Mar 14, 2022

romainiac commented Mar 16, 2022

audryhsu commented Mar 17, 2022

iiian commented Apr 24, 2022 • edited Loading

nathanpovo commented May 16, 2022 • edited Loading

bhat-anusha commented May 16, 2022

RohanVDeshpande commented May 17, 2022

RohanVDeshpande commented May 17, 2022

hubologist24 commented May 17, 2022

rehlucena88 commented May 24, 2022

michalbidzinski1 commented Jun 2, 2022 • edited Loading

vishnupeas commented Jun 19, 2022

87prashant commented Jun 23, 2022 • edited Loading

87prashant commented Jun 23, 2022

adityavartak07 commented Jun 26, 2022

lucaszarza commented Jul 16, 2022

danielcaze commented Aug 3, 2022

87prashant commented Aug 3, 2022

ianpegg commented Sep 26, 2022 • edited Loading

HuyyNguyenz commented Sep 29, 2022

jerlam06 commented Oct 27, 2022

hoa-nguyen-bk commented Nov 21, 2022

olsonperrensen commented Dec 7, 2022 • edited Loading

gaurpulkit commented Mar 15, 2023

independenceee commented Jul 4, 2023

Is your proposal related to a problem?

Describe the solution you'd like

Describe alternatives you've considered

Additional context

GabrielFMPinheiro commented Jan 23, 2024

bennettdams commented Dec 18, 2020 •

edited

Loading

PrajjwalDatir commented Dec 19, 2020 •

edited

Loading

nurshom commented Dec 29, 2021 •

edited

Loading

ianisms commented Jan 26, 2022 •

edited

Loading

Bizzle-Dapp commented Mar 11, 2022 •

edited

Loading

iiian commented Apr 24, 2022 •

edited

Loading

nathanpovo commented May 16, 2022 •

edited

Loading

michalbidzinski1 commented Jun 2, 2022 •

edited

Loading

87prashant commented Jun 23, 2022 •

edited

Loading

ianpegg commented Sep 26, 2022 •

edited

Loading

olsonperrensen commented Dec 7, 2022 •

edited

Loading