Closed robfarmergt closed 5 months ago
This seems to be happening when we add any new npm packages. If we back out the two new packages that we were trying to use then it deploys just fine.
We have confirmed that all of our WebApp instances are using the same versions of npm, node and gulp. This issue is only happening in one of our instances but not the other.
Wondering if there are any suggestions for us on this. Still an issue in one of our environments which is preventing us from deploying. @davidebbo
Have you tried using a newer npm? 1.4.9 is super old.
We can try that next time. We rolled back to always using default NPM because we were having other issues when overriding them and couldn't get it to consistently deploy across all of our environments. Here is the past issue: #2285
Any recommendations on which Node & NPM versions to specify?
I suggest using the latest LTS build, which is currently Node v6.9.4. And that maps to npm 3.10.10 (so you shouldn't have to explicitly specify npm if yo pick Node).
Hey folks!
I'm trying to move our gulp build to Azure and have added this lines to deploy.sh
# 4. Run Gulp Task
if [ -e "$DEPLOYMENT_TARGET/gulpfile.js" ]; then
cd "$DEPLOYMENT_TARGET"
eval ./node_modules/.bin/gulp
exitWithMessageOnError "gulp failed"
cd - > /dev/null
fi
And looks like when gulp runs we have this error -
kudu ENOTSUP: operation not supported on socket, scandir
I have tried node and npm version change and it does not help. After googling - there might be related issue - https://github.com/projectkudu/kudu/issues/1787 But I don't know how it relates to gulp. Node 6.9.5 Npm 3.10.10 Gulp 3.9.1
Hi
If the problem persists and is related to running it on Azure App Service, please open a support incident in Azure: https://learn.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request
This way we can better track and assist you on this case
Thanks,
Joaquin Vano Azure App Service
We are seeing this error and I have looked through a few of the closed issues here but can't see a recent one that might be related.
We have successfully deployed this codebase to one WebApp in Azure but now we're trying to deploy to a second one and we're getting this error.
Here's the deployment log output: