npm bs: webpack loop when executed in docker (Out of the box)

[jmsherry]

Hi guys,

System: OSx 10.11.6 El Capitan using docker for mac

If you mern init a new project; npm i; docker-compose build; then docker-compose up the script gets as far as running npm run build:server then it starts to write both the cache-busted header bg image and a .webpack.res.<cache-buster>.js file straight into the root of the project. The webpack task never completes and you have to kill it.

Love the project, btw! Any help would be greatly appreciated

Thanks

[zoalst]

I ran into a similar issue on Ubuntu and fixed it by adding BABEL_DISABLE_CACHE=1 to the start:prod, build, and build:server scripts in package.json
It should look like this:

    "start:prod": "cross-env BABEL_DISABLE_CACHE=1 NODE_ENV=production node index.js",
    "bs": "npm run clean && npm run build && npm run build:server && npm run start:prod",
    "build": "cross-env  BABEL_DISABLE_CACHE=1 NODE_ENV=production webpack --config webpack.config.prod.js",
    "build:server": "cross-env  BABEL_DISABLE_CACHE=1 NODE_ENV=production webpack --config webpack.config.server.js",

Hope that helps.

[jmsherry]

@zacharystenger Thanks man. I just ran it under the test conditions I mentioned above with the package.json altered to match what you have there, but tragically the issues still remain.

Cheers for the info though. 👍