Since the node docker containers are extremely slow at doing an npm install, and often crash, MS support has been advising me to use the kudu bash tool to rerun npm manually.
Running npm in that shell results in an extremely old npm version (3.10.10), and the resulting node_modules folder structure is not compatible with the runtime node version.
You have to use the other command to do npm installs from the bash shell properly ("/opt/nodejs/8.1.0/bin/node" "/opt/npm/5.0.3/node_modules/npm/bin/npm-cli.js" install --production)
Why doesn't the default npm match the npm used by the build script? Why does npm install timeout/crash on even simple node apps?
Since the node docker containers are extremely slow at doing an npm install, and often crash, MS support has been advising me to use the kudu bash tool to rerun npm manually.
Running npm in that shell results in an extremely old npm version (3.10.10), and the resulting node_modules folder structure is not compatible with the runtime node version.
You have to use the other command to do npm installs from the bash shell properly ("/opt/nodejs/8.1.0/bin/node" "/opt/npm/5.0.3/node_modules/npm/bin/npm-cli.js" install --production)
Why doesn't the default npm match the npm used by the build script? Why does npm install timeout/crash on even simple node apps?