When deploying repos created with a node version differing from that of the app service, and containing package-lock.json, the app service is often unable to do "npm install" correctly. It will complete, but not install the correct modules, and the node runtime will fail.
I modified my kudu deployment script to remove package-lock.json before the npm install.
Also, the purpose and behavior of package-lock.json is somewhat in flux: npm/npm#18103
At the very least, maybe add a warning to only use package-lock if you are deving on the exact same version your app service is running.
When deploying repos created with a node version differing from that of the app service, and containing package-lock.json, the app service is often unable to do "npm install" correctly. It will complete, but not install the correct modules, and the node runtime will fail.
I modified my kudu deployment script to remove package-lock.json before the npm install.
Also, the purpose and behavior of package-lock.json is somewhat in flux: npm/npm#18103
At the very least, maybe add a warning to only use package-lock if you are deving on the exact same version your app service is running.