Closed setheal closed 3 years ago
Hey @jvsinghk I looked on your screenshot and it seems like nodemon is not ignoring the build folder that's why it keep restarting. Can you check that you have this part in the dev
script : --ignore 'build/*'
? Thank you.
EDIT: nevermind I just saw it in your screenshot... Can you run a npm run build
and check if another files/folder is modified by the command ?
Hey, @setheal I do have that. Before running npm run build
I had some changes in package-lock.json
and yarn.lock
which I got after running npm install
and yarn
respectively. After running npm run build
the build folder gets updated. and then I ran npm run dev
which runs into the same issue. I have committed my changes if you allow me I can push them to your branch. That might help you to reproduce the bug.
@jvsinghk yes, push them pelase
@setheal pushed it. review it, please
Hye @jvsinghk everythings works as a charm on my side. Are you still encountering this issue ?
Everything works as expected on my side, I'm really confused. Which OS are you running ?
hey @jvsinghk can you check the latest version please ?
hey @jvsinghk can you check the latest version, please?
hey, @setheal checked the latest version, doesn't work.
Resolve #7
I added the server side rendering thanks to
ReactDOMServer
, I also modified theindex.js
of React to get the possibility to hydrate the dom if needed.I took the liberty of modifying the development server because the server side rendering depends of the react app being built. To start the development server it's now advised to use
npm run dev
.I hope this solution is what you wanted 🚀