npm run start not using new compiled files

[alison985]

Hi. I originally filed a ticket in the Mozilla fork about this mozilla#410 but we still haven't found a solution. @kocsmy I'd appreciate any thoughts. Do you have any ideas on what else I could try?

cc: @jezdez

[arikfr]

After running npm run start, what URL do you open in the browser?

[alison985]

@arikfr localhost:5000/ which turns to http://0.0.0.0:5000/

[arikfr]

npm run start runs webpack-dev-server which serves the frontend code from in memory cache on port 8080 (this is the default). It also proxies API requests to the Flask server.

When you load localhost:5000 you are calling the Flask server, which can't use this cache and loads the frontend code from client/dist. npm run watch will constantly watch for changes in client/app and rebuild the files in client/dist.

Although for frontend development, my recommendation is to use npm start as it also live reloads the browser on changes.

Just to clarify you need to use npm run watch or npm run start - not both.

[alison985]

Thanks!