Npm Err Move It Away and Try Again Npm

[Node.js][Mobile Service] Azure Mobile Service deployment errors when using 'git button'

• Question

• I have a node.js mobile service which I 'git cloned' to my local workstation. I did 'npm install request --save' and a git commit. Now I'chiliad getting errors when I deploy with 'git push'. I run into ENOTSUP errors, so does that mean that npm asking-hope is not supported?

  Here are the exact steps I performed.

  1. git clone [azure mobile service git url]
  2. cd [working directory]/service
  3. npm install [module name] --save
  4. git commit -am "Add npm asking module" && git push

  My package.json file is:

  {   "name": "myazureapp",   "version": "ane.0.0",   "description": "myazureapp - hosted on Windows Azure Mobile Services",   "main": "server.js",   "engines": {     "node": ">= 0.viii.19"   },   "dependencies": {     "azure": "^0.10.six",     "basic-logger": "^0.4.4",     "bignumber": "^1.1.0",     "bing": "^0.1.0",     "braintree": "^1.35.1",     "facebook-node": "0.0.3",     "geobing": "^0.one.3",     "mobileservice-config": "^ane.0.0",     "moment": "^2.11.two",     "node-uuid": "^i.4.seven",     "paypal-adaptive": "^0.iv.ii",     "paypal-ec": "^0.2.7",     "paypal-ipn": "^3.0.0",     "q": "^1.four.i",     "request": "2.ix.152",     "request-promise": "^2.0.0",     "sendgrid": "^two.0.0",     "sprintf": "^0.one.five",     "underscore": "^one.eight.iii",     "xml2js": "^0.4.16"   },   "devDependencies": {},   "scripts": {},   "writer": "unknown",   "licenses": [],   "keywords": [] }

  And here is what 'git push' reveals:

  me@iMac:~/coding/git/mymobileapp/service$ git commit -am "Add npm modules" && git push [master ee243be] Add npm modules  one file changed, iii insertions(+), 3 deletions(-) Counting objects: 4, done. Delta compression using upwardly to eight threads. Compressing objects: 100% (4/4), done. Writing objects: 100% (iv/iv), 386 bytes | 0 bytes/southward, done. Total 4 (delta 3), reused 0 (delta 0) remote: Updating branch 'master'. remote: Updating submodules. remote: Preparing deployment for commit id 'ee243bea61'. remote: Running custom deployment control... remote: Running deployment command... remote: Treatment Basic Spider web Site deployment. remote: KuduSync.Cyberspace from: 'D:\habitation\site\repository\service' to: 'D:\home\site\wwwroot\App_Data\config\scripts' remote: Copying file: 'parcel.json' remote: Looking for app.js/server.js nether site root. remote: Missing server.js/app.js files, web.config is not generated remote: Node.js versions bachelor on the platform are: 0.vi.20, 0.8.2, 0.eight.19, 0.8.26, 0.8.27, 0.eight.28, 0.10.5, 0.10.eighteen, 0.ten.21, 0.x.24, 0.ten.26, 0.ten.28, 0.10.29, 0.10.31, 0.10.32, 0.x.40, 0.12.0, 0.12.two, 0.12.iii, 0.12.vi, four.0.0, 4.1.0, 4.i.2, 4.ii.ane, 4.ii.2, 4.2.iii, four.ii.4, 4.3.0, 5.0.0, v.one.1, 5.three.0, v.4.0, 5.5.0, five.half-dozen.0. remote: Selected node.js version v.6.0. Employ package.json file to cull a dissimilar version. remote: Selected npm version 3.6.0 remote: Updating iisnode.yml at D:\dwelling\site\wwwroot\App_Data\config\scripts\iisnode.yml remote: npm WARN package.json mymobileapp@i.0.0 No repository field. remote: npm WARN parcel.json mymobileapp@one.0.0 No README data remote: npm WARN package.json basic-logger@0.4.iv No repository field. remote: npm http GET https://registry.npmjs.org/asking-promise remote: npm http GET https://registry.npmjs.org/asking remote: npm http 304 https://registry.npmjs.org/request-promise remote: npm http 304 https://registry.npmjs.org/request remote: npm http GET https://registry.npmjs.org/request-promise/-/request-promise-ii.0.0.tgz remote: npm http Go https://registry.npmjs.org/request/-/asking-ii.9.152.tgz remote: npm http 200 https://registry.npmjs.org/request-promise/-/asking-hope-2.0.0.tgz remote: npm http 200 https://registry.npmjs.org/asking/-/request-2.9.152.tgz remote: npm http Go https://registry.npmjs.org/lodash remote: npm http Become https://registry.npmjs.org/bluebird remote: npm http 304 https://registry.npmjs.org/bluebird remote: npm http 304 https://registry.npmjs.org/lodash remote: npm http Become https://registry.npmjs.org/aws-sign2 remote: npm http GET https://registry.npmjs.org/aws4 remote: npm http GET https://registry.npmjs.org/caseless remote: npm http GET https://registry.npmjs.org/combined-stream remote: npm http Go https://registry.npmjs.org/class-information remote: npm http Go https://registry.npmjs.org/bl remote: npm http Go https://registry.npmjs.org/extend remote: npm http Get https://registry.npmjs.org/forever-agent remote: npm http Become https://registry.npmjs.org/har-validator remote: npm http Become https://registry.npmjs.org/http-signature remote: npm http Go https://registry.npmjs.org/is-typedarray remote: npm http GET https://registry.npmjs.org/isstream remote: npm http Become https://registry.npmjs.org/json-stringify-safe remote: npm http Become https://registry.npmjs.org/hawk remote: npm http GET https://registry.npmjs.org/mime-types remote: npm http Become https://registry.npmjs.org/oauth-sign remote: npm http GET https://registry.npmjs.org/stringstream remote: npm http GET https://registry.npmjs.org/qs remote: npm http Become https://registry.npmjs.org/tough-cookie remote: npm http GET https://registry.npmjs.org/tunnel-agent remote: npm http 304 https://registry.npmjs.org/aws-sign2 remote: npm http 304 https://registry.npmjs.org/aws4 remote: npm http 304 https://registry.npmjs.org/caseless remote: npm http 304 https://registry.npmjs.org/combined-stream remote: npm http 304 https://registry.npmjs.org/bl remote: npm http 304 https://registry.npmjs.org/har-validator remote: npm http 304 https://registry.npmjs.org/grade-data remote: npm http 304 https://registry.npmjs.org/extend remote: npm http 304 https://registry.npmjs.org/is-typedarray remote: npm http 304 https://registry.npmjs.org/forever-amanuensis remote: npm http 304 https://registry.npmjs.org/http-signature remote: npm http 304 https://registry.npmjs.org/isstream remote: npm http 304 https://registry.npmjs.org/oauth-sign remote: npm http 304 https://registry.npmjs.org/json-stringify-safe remote: npm http 304 https://registry.npmjs.org/hawk remote: npm http 304 https://registry.npmjs.org/tough-cookie remote: npm http 304 https://registry.npmjs.org/mime-types remote: npm http 304 https://registry.npmjs.org/stringstream remote: npm http 304 https://registry.npmjs.org/tunnel-agent remote: npm http 304 https://registry.npmjs.org/qs remote: npm http Get https://registry.npmjs.org/delayed-stream remote: npm http 304 https://registry.npmjs.org/delayed-stream remote: npm http GET https://registry.npmjs.org/mime-db remote: npm http Get https://registry.npmjs.org/async remote: npm http 304 https://registry.npmjs.org/mime-db remote: npm http 304 https://registry.npmjs.org/async remote: npm http Go https://registry.npmjs.org/readable-stream remote: npm http Become https://registry.npmjs.org/lru-cache remote: npm http 304 https://registry.npmjs.org/lru-enshroud remote: npm http 304 https://registry.npmjs.org/readable-stream remote: npm http Get https://registry.npmjs.org/assert-plus remote: npm http Go https://registry.npmjs.org/jsprim remote: npm http GET https://registry.npmjs.org/sshpk remote: npm http 304 https://registry.npmjs.org/assert-plus remote: npm http 304 https://registry.npmjs.org/sshpk remote: npm http 304 https://registry.npmjs.org/jsprim remote: npm http Go https://registry.npmjs.org/pinkie-promise remote: npm http Go https://registry.npmjs.org/chalk remote: npm http GET https://registry.npmjs.org/commander remote: npm http Get https://registry.npmjs.org/is-my-json-valid remote: npm http GET https://registry.npmjs.org/verror remote: npm http GET https://registry.npmjs.org/extsprintf remote: npm http GET https://registry.npmjs.org/json-schema remote: npm http 304 https://registry.npmjs.org/pinkie-promise remote: npm http 304 https://registry.npmjs.org/commander remote: npm http 304 https://registry.npmjs.org/chalk remote: npm http 304 https://registry.npmjs.org/is-my-json-valid remote: npm http 304 https://registry.npmjs.org/verror remote: npm http 304 https://registry.npmjs.org/extsprintf remote: npm http 304 https://registry.npmjs.org/json-schema remote: npm http Go https://registry.npmjs.org/pinkie remote: npm http Go https://registry.npmjs.org/cryptiles remote: npm http Become https://registry.npmjs.org/sntp remote: npm http Become https://registry.npmjs.org/has-ansi remote: npm http Get https://registry.npmjs.org/strip-ansi remote: npm http GET https://registry.npmjs.org/supports-color remote: npm http Get https://registry.npmjs.org/boom remote: npm http Get https://registry.npmjs.org/hoek remote: npm http GET https://registry.npmjs.org/ansi-styles remote: npm http GET https://registry.npmjs.org/escape-string-regexp remote: npm http GET https://registry.npmjs.org/isarray remote: npm http GET https://registry.npmjs.org/process-nextick-args remote: npm http GET https://registry.npmjs.org/string_decoder remote: npm http GET https://registry.npmjs.org/util-deprecate remote: npm http Become https://registry.npmjs.org/core-util-is remote: npm http Go https://registry.npmjs.org/inherits remote: npm http 304 https://registry.npmjs.org/pinkie remote: npm http 304 https://registry.npmjs.org/cryptiles remote: npm http 304 https://registry.npmjs.org/has-ansi remote: npm http 304 https://registry.npmjs.org/sntp remote: npm http 304 https://registry.npmjs.org/ansi-styles remote: npm http 304 https://registry.npmjs.org/boom remote: npm http 304 https://registry.npmjs.org/strip-ansi remote: npm http 304 https://registry.npmjs.org/supports-colour remote: npm http 304 https://registry.npmjs.org/hoek remote: npm http 304 https://registry.npmjs.org/process-nextick-args remote: npm http 304 https://registry.npmjs.org/escape-string-regexp remote: npm http 304 https://registry.npmjs.org/isarray remote: npm http 304 https://registry.npmjs.org/util-deprecate remote: npm http 304 https://registry.npmjs.org/string_decoder remote: npm http 304 https://registry.npmjs.org/inherits remote: npm http 304 https://registry.npmjs.org/cadre-util-is remote: npm http GET https://registry.npmjs.org/graceful-readlink remote: npm http 304 https://registry.npmjs.org/svelte-readlink remote: npm http GET https://registry.npmjs.org/ansi-regex remote: npm http 304 https://registry.npmjs.org/ansi-regex remote: glob fault { [Error: ENOTSUP: performance not supported on socket, scandir 'D:\home\site\wwwroot\App_Data\config\scripts\node_modules\asking-promise\node_modules\request\node_modules\http-signature\node_modules\sshpk\human\man1\sshpk-conv.1'] remote:   errno: -4049, remote:   lawmaking: 'ENOTSUP', remote:   syscall: 'scandir', remote:   path: 'D:\\dwelling\\site\\wwwroot\\App_Data\\config\\scripts\\node_modules\\asking-hope\\node_modules\\request\\node_modules\\http-signature\\node_modules\\sshpk\\man\\man1\\sshpk-conv.1' } remote: glob error { [Error: ENOTSUP: operation not supported on socket, scandir 'D:\home\site\wwwroot\App_Data\config\scripts\node_modules\request-promise\node_modules\request\node_modules\http-signature\node_modules\sshpk\man\man1\sshpk-sign.ane'] remote:   errno: -4049, remote:   lawmaking: 'ENOTSUP', remote:   syscall: 'scandir', remote:   path: 'D:\\domicile\\site\\wwwroot\\App_Data\\config\\scripts\\node_modules\\request-hope\\node_modules\\request\\node_modules\\http-signature\\node_modules\\sshpk\\man\\man1\\sshpk-sign.one' } remote: glob error { [Error: ENOTSUP: operation not supported on socket, scandir 'D:\domicile\site\wwwroot\App_Data\config\scripts\node_modules\asking-hope\node_modules\request\node_modules\http-signature\node_modules\sshpk\man\man1\sshpk-verify.i'] remote:   errno: -4049, remote:   lawmaking: 'ENOTSUP', remote:   syscall: 'scandir', remote:   path: 'D:\\home\\site\\wwwroot\\App_Data\\config\\scripts\\node_modules\\request-hope\\node_modules\\request\\node_modules\\http-signature\\node_modules\\sshpk\\man\\man1\\sshpk-verify.1' } remote: glob error { [Fault: ENOTSUP: functioning not supported on socket, scandir 'D:\home\site\wwwroot\App_Data\config\scripts\node_modules\asking-hope\node_modules\request\node_modules\http-signature\node_modules\sshpk\bin\sshpk-conv'] remote:   errno: -4049, remote:   code: 'ENOTSUP', remote:   syscall: 'scandir', remote:   path: 'D:\\home\\site\\wwwroot\\App_Data\\config\\scripts\\node_modules\\request-promise\\node_modules\\request\\node_modules\\http-signature\\node_modules\\sshpk\\bin\\sshpk-conv' } remote: glob error { [Mistake: ENOTSUP: functioning non supported on socket, scandir 'D:\home\site\wwwroot\App_Data\config\scripts\node_modules\request-promise\node_modules\asking\node_modules\http-signature\node_modules\sshpk\bin\sshpk-sign'] remote:   errno: -4049, remote:   code: 'ENOTSUP', remote:   syscall: 'scandir', remote:   path: 'D:\\abode\\site\\wwwroot\\App_Data\\config\\scripts\\node_modules\\request-promise\\node_modules\\asking\\node_modules\\http-signature\\node_modules\\sshpk\\bin\\sshpk-sign' } remote: glob mistake { [Error: ENOTSUP: operation not supported on socket, scandir 'D:\home\site\wwwroot\App_Data\config\scripts\node_modules\request-promise\node_modules\request\node_modules\http-signature\node_modules\sshpk\bin\sshpk-verify'] remote:   errno: -4049, remote:   lawmaking: 'ENOTSUP', remote:   syscall: 'scandir', remote:   path: 'D:\\dwelling house\\site\\wwwroot\\App_Data\\config\\scripts\\node_modules\\asking-promise\\node_modules\\asking\\node_modules\\http-signature\\node_modules\\sshpk\\bin\\sshpk-verify' } remote: npm ERR! error rolling back Fault: EPERM: functioning not permitted, rmdir 'D:\home\site\wwwroot\App_Data\config\scripts\node_modules\request-promise\node_modules\asking\node_modules\http-signature\node_modules\jsprim\node_modules\json-schema' remote: npm ERR! error rolling back     at Error (native) remote: npm ERR! fault rolling dorsum  json-schema@0.two.ii { [Error: EPERM: operation not permitted, rmdir 'D:\home\site\wwwroot\App_Data\config\scripts\node_modules\request-hope\node_modules\asking\node_modules\http-signature\node_modules\jsprim\node_modules\json-schema'] remote: npm ERR! error rolling back   errno: -4048, remote: npm ERR! mistake rolling back   code: 'EPERM', remote: npm ERR! fault rolling dorsum   syscall: 'rmdir', remote: npm ERR! mistake rolling dorsum   path: 'D:\\habitation\\site\\wwwroot\\App_Data\\config\\scripts\\node_modules\\request-promise\\node_modules\\request\\node_modules\\http-signature\\node_modules\\jsprim\\node_modules\\json-schema' } remote: npm http Become https://registry.npmjs.org/generate-office remote: npm http Go https://registry.npmjs.org/generate-object-property remote: npm http GET https://registry.npmjs.org/jsonpointer remote: npm http GET https://registry.npmjs.org/xtend remote: npm ERR! error rolling back Error: EPERM: functioning not permitted, unlink 'D:\dwelling\site\wwwroot\App_Data\config\scripts\node_modules\asking-promise\node_modules\request\node_modules\http-signature\node_modules\jsprim\node_modules' remote: npm ERR! error rolling dorsum     at Error (native) remote: npm ERR! mistake rolling back  jsprim@1.2.2 { [Error: EPERM: operation not permitted, unlink 'D:\dwelling house\site\wwwroot\App_Data\config\scripts\node_modules\request-promise\node_modules\request\node_modules\http-signature\node_modules\jsprim\node_modules'] remote: npm ERR! error rolling dorsum   errno: -4048, remote: npm ERR! error rolling dorsum   code: 'EPERM', remote: npm ERR! error rolling back   syscall: 'unlink', remote: npm ERR! error rolling back   path: 'D:\\home\\site\\wwwroot\\App_Data\\config\\scripts\\node_modules\\request-promise\\node_modules\\request\\node_modules\\http-signature\\node_modules\\jsprim\\node_modules' } remote: npm http 304 https://registry.npmjs.org/generate-function remote: npm http 304 https://registry.npmjs.org/generate-object-holding remote: npm http 304 https://registry.npmjs.org/xtend remote: npm http 304 https://registry.npmjs.org/jsonpointer remote: npm ERR! Mistake: ENOENT: no such file or directory, chmod 'D:\home\site\wwwroot\App_Data\config\scripts\node_modules\request-promise\node_modules\request\node_modules\har-validator\node_modules\is-my-json-valid\node_modules\xtend\LICENCE' remote: npm ERR!     at Error (native) remote: npm ERR! If you need help, you may written report this *entire* log, remote: npm ERR! including the npm and node versions, at: remote: npm ERR!     <http: github.com="" issues="" npm=""> remote:  remote: npm ERR! System Windows_NT 6.2.9200 remote: npm ERR! control "D:\\Program Files (x86)\\nodejs\\five.half dozen.0\\node.exe" "D:\\Plan Files (x86)\\npm\\ane.iv.9\\node_modules\\npm\\bin\\npm-cli.js" "install" "--production" remote: npm ERR! cwd D:\dwelling\site\wwwroot\App_Data\config\scripts remote: npm ERR! node -v v5.6.0 remote: npm ERR! npm -v 1.4.ix remote: npm ERR! path D:\dwelling\site\wwwroot\App_Data\config\scripts\node_modules\request-promise\node_modules\request\node_modules\har-validator\node_modules\is-my-json-valid\node_modules\xtend\LICENCE remote: npm ERR! syscall chmod remote: npm ERR! fstream_path D:\home\site\wwwroot\App_Data\config\scripts\node_modules\request-promise\node_modules\request\node_modules\har-validator\node_modules\is-my-json-valid\node_modules\xtend\LICENCE remote: npm ERR! fstream_type File remote: npm ERR! fstream_class FileWriter remote: npm ERR! fstream_finish_call chmod remote: npm ERR! code ENOENT remote: npm ERR! errno -4058 remote: npm ERR! fstream_stack c:\Program Files (x86)\npm\ane.4.9\node_modules\npm\node_modules\fstream\lib\writer.js:305:xix remote: npm ERR! fstream_stack FSReqWrap.oncomplete (fs.js:82:15) remote: npm ERR! Error: ENOENT: no such file or directory, lstat 'D:\home\site\wwwroot\App_Data\config\scripts\node_modules\asking-promise\node_modules\request\node_modules\har-validator\node_modules\is-my-json-valid\node_modules\generate-function\example.js' remote: npm ERR!     at Error (native) remote: npm ERR! If yous need assist, you may written report this *unabridged* log, remote: npm ERR! including the npm and node versions, at: remote: npm ERR!     <http: github.com="" issues="" npm=""> remote:  remote: npm ERR! System Windows_NT vi.2.9200 remote: npm ERR! command "D:\\Programme Files (x86)\\nodejs\\5.6.0\\node.exe" "D:\\Programme Files (x86)\\npm\\i.4.nine\\node_modules\\npm\\bin\\npm-cli.js" "install" "--production" remote: npm ERR! cwd D:\home\site\wwwroot\App_Data\config\scripts remote: npm ERR! node -five v5.half dozen.0 remote: npm ERR! npm -5 1.iv.9 remote: npm ERR! path D:\dwelling\site\wwwroot\App_Data\config\scripts\node_modules\request-promise\node_modules\request\node_modules\har-validator\node_modules\is-my-json-valid\node_modules\generate-function\example.js remote: npm ERR! syscall lstat remote: npm ERR! fstream_path D:\home\site\wwwroot\App_Data\config\scripts\node_modules\request-hope\node_modules\asking\node_modules\har-validator\node_modules\is-my-json-valid\node_modules\generate-function\example.js remote: npm ERR! fstream_type File remote: npm ERR! fstream_class FileWriter remote: npm ERR! code ENOENT remote: npm ERR! errno -4058 remote: npm ERR! fstream_stack c:\Programme Files (x86)\npm\1.iv.9\node_modules\npm\node_modules\fstream\lib\writer.js:284:26 remote: npm ERR! fstream_stack FSReqWrap.oncomplete (fs.js:82:fifteen) remote: npm ERR! error rolling back Fault: EPERM: functioning not permitted, unlink 'D:\home\site\wwwroot\App_Data\config\scripts\node_modules\asking-promise\node_modules\asking\node_modules\har-validator' remote: npm ERR! error rolling back     at Error (native) remote: npm ERR! error rolling dorsum  har-validator@2.0.6 { [Error: EPERM: functioning not permitted, unlink 'D:\home\site\wwwroot\App_Data\config\scripts\node_modules\request-promise\node_modules\request\node_modules\har-validator'] remote: npm ERR! error rolling dorsum   errno: -4048, remote: npm ERR! error rolling back   code: 'EPERM', remote: npm ERR! error rolling dorsum   syscall: 'unlink', remote: npm ERR! mistake rolling back   path: 'D:\\home\\site\\wwwroot\\App_Data\\config\\scripts\\node_modules\\request-promise\\node_modules\\request\\node_modules\\har-validator' } remote: npm ERR! EEXIST: file already exists, mkdir 'D:\home\site\wwwroot\App_Data\config\scripts\node_modules\request-hope\node_modules\lodash\object' remote: File exists: D:\home\site\wwwroot\App_Data\config\scripts\node_modules\asking-promise\node_modules\lodash\object remote: Motion it abroad, and try again.  remote:  remote: npm ERR! System Windows_NT vi.2.9200 remote: npm ERR! command "D:\\Program Files (x86)\\nodejs\\5.6.0\\node.exe" "D:\\Program Files (x86)\\npm\\1.4.ix\\node_modules\\npm\\bin\\npm-cli.js" "install" "--production" remote: npm ERR! cwd D:\home\site\wwwroot\App_Data\config\scripts remote: npm ERR! node -v v5.6.0 remote: npm ERR! npm -5 1.4.ix remote: npm ERR! path D:\home\site\wwwroot\App_Data\config\scripts\node_modules\request-promise\node_modules\lodash\object remote: npm ERR! syscall mkdir remote: npm ERR! fstream_path D:\home\site\wwwroot\App_Data\config\scripts\node_modules\request-hope\node_modules\lodash\object\transform.js remote: npm ERR! fstream_type File remote: npm ERR! fstream_class FileWriter remote: npm ERR! code EEXIST remote: npm ERR! errno -4075 remote: npm ERR! fstream_stack c:\Program Files (x86)\npm\ane.four.9\node_modules\npm\node_modules\fstream\lib\writer.js:171:23 remote: npm ERR! fstream_stack c:\Program Files (x86)\npm\1.4.ix\node_modules\npm\node_modules\mkdirp\index.js:37:53 remote: npm ERR! fstream_stack FSReqWrap.oncomplete (fs.js:82:xv) remote: npm ERR! Error: ENOTSUP: operation not supported on socket, scandir 'D:\home\site\wwwroot\App_Data\config\scripts\node_modules\request-promise\node_modules\asking\node_modules\http-signature\node_modules\sshpk\man\man1\sshpk-conv.1' remote: npm ERR!     at Error (native) remote: npm ERR! If you need help, yous may report this *entire* log, remote: npm ERR! including the npm and node versions, at: remote: An error has occurred during web site deployment. remote: npm ERR!     <http: github.com="" issues="" npm=""> remote:  remote: npm ERR! System Windows_NT 6.2.9200 remote: npm ERR! command "D:\\Plan Files (x86)\\nodejs\\5.6.0\\node.exe" "D:\\Program Files (x86)\\npm\\ane.iv.nine\\node_modules\\npm\\bin\\npm-cli.js" "install" "--production" remote: npm ERR! cwd D:\home\site\wwwroot\App_Data\config\scripts remote: npm ERR! node -v v5.6.0 remote: npm ERR! npm -five 1.four.nine remote: npm ERR! path D:\abode\site\wwwroot\App_Data\config\scripts\node_modules\request-promise\node_modules\request\node_modules\http-signature\node_modules\sshpk\human\man1\sshpk-conv.1 remote: npm ERR! syscall scandir remote: npm ERR! code ENOTSUP remote: npm ERR! errno -4049 remote: npm ERR!  remote: npm ERR! Additional logging details tin exist institute in: remote: npm ERR!     D:\habitation\site\wwwroot\App_Data\config\scripts\npm-debug.log remote: npm ERR! not ok code 0 remote:  remote: Error - Changes committed to remote repository just deployment to website failed. To https://mymobileapp.scm.azure-mobile.net/mymobileapp.git    05525e5..ee243be  chief -> primary</http:></http:></http:>

  • Moved past Monday, February xv, 2022 viii:19 PM question is with regard to Mobile Services environment
  • Edited by Gary Liu - MSFT Tuesday, February 16, 2022 ane:24 AM edit championship
  • Moved by Peter Pan - MSFT Microsoft contingent staff Friday, July i, 2022 3:00 AM Move to new forum
  • Edited by Peter Pan - MSFT Microsoft contingent staff Friday, July 1, 2022 6:24 AM add title tag

Answers

• When we deploy Node.js backend application to Azure Mobile Service via local Git repository, Azure will run the deployment job called "ZumoDeploy.cmd", you can notice the file ".deployment" in your root directory , and the content in the file is :

  [config] command = ..\ZumoDeploy.cmd

   We leverage Kudu console site of your mobile service application at the url of "https://<your_mobile_service_name>.scm.azure-mobile.net/DebugConsole", locate to the path "D:\home\site", we can find the task script, and the 25th line in this file forces utilize a sometime version of npm to install all your dependencies, which raised the issue.

  You can simply modify the line to a newer version, e.g.:

  Ready NPM_JS_PATH=%ProgramFiles(x86)%\npm\3.iii.12\node_modules\npm\bin\npm-cli.js

  And so, when you deploy the application, the deployment job volition use the newer npm version.

  Otherwise, y'all tin can comment this script, and custom the NPM_JS_PATH in your mobile service repository, you tin can refer to https://social.msdn.microsoft.com/Forums/azure/en-US/068ef026-f80d-4bf8-9f40-5d1af33a1024/git-deployment-fails-with-npm-error-when-resolving-a-package-version-containing-a-?forum=windowsazurewebsitespreview, in this thread there is a method to specify the npm version in your deployment task.
  

  • Proposed as reply by Gary Liu - MSFT Wed, February 17, 2022 i:17 AM
  • Marked every bit reply past Gary Liu - MSFT Mon, February 22, 2022 8:52 AM

davidsonengropose.blogspot.com

Source: https://social.msdn.microsoft.com/Forums/sqlserver/en-US/d929d814-41c5-4373-8530-2a76aba554b3/nodejsmobile-service-azure-mobile-service-deployment-errors-when-using-git-push

Share this post