Yeah it showing same thing.
is your remote branch up to date, if yes and still getting same error, try doing locally
I am facing a similar issue
Hello @Yash_Patel ,
Whats the reason for running npm start ???
The frontend app will start but wont work.
Because of some security configurations, the application will only work when accesed behind the proxy.
If you want to test your local changes ,
running docker-compose -f dev.docker-compose.yml up -d should work prety fine as it mounts your local source code into the frontend container, so it should hot reload when you make any local change.
see full instructions on the ReadMe page
4 Likes
@Yash_Patel You should try to just go to localhost in your browser, not visiting port 3000… This should be enough… There is no need for you to run npm start…
just start the docker containers using docker-compose -f dev.docker-compose up -d and then visit localhost in your browser…
Yeah I have tried setup through wsl and it is working on localhost
3 Likes
are you good to go now ??
Right now busy in some daily stuff giving you updates in few times
2 Likes