Microsoft Azure - Gulp 3.8.10 does not work on new instance of web app

I am using a new instance of a web application with Node 12.3 and NPM 2.9.1. Gulp The PATH seems to be set to D: \ Program Files (x86) \ gulp \ 3.8.10. I believe Gulp 3.8.10 has a bug that should be fixed with an upgrade to 3.8.11. I can't use Gulp until this is developed ... If there is no other way to handle this? Any help from the azure team would be greatly appreciated. Deploying with Gulp has been a thorn in my side on this platform. I'm trying to use vNext deployment with Angular and WebApi ... My Gulp CI builds can't move forward because of this. Thanks to everyone who can help!

I think this issue is flagged here https://github.com/gulpjs/gulp/issues/893

Kudu Remote Execution Console
Type 'exit' then hit 'enter' to get a new CMD process.
Type 'cls' to clear the console

Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.

D:\home>gulp -v
module.js:338
    throw err;
          ^
Error: Cannot find module 'D:\Program Files (x86)\gulp\3.8.10\node_modules\gulp\node_modules\v8flags\3.28.73.flags.json'
    at Function.Module._resolveFilename (module.js:336:15)
    at Function.Module._load (module.js:278:25)
    at Module.require (module.js:365:17)
    at require (module.js:384:17)
    at Object.<anonymous> (D:\Program Files (x86)\gulp\3.8.10\node_modules\gulp\bin\gulp.js:25:22)
    at Module._compile (module.js:460:26)
    at Object.Module._extensions..js (module.js:478:10)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Function.Module.runMain (module.js:501:10)

      

+3


source to share


2 answers


Short version:

You can install your own version of gulp wherever you go for example D:\home\npm_tools\

and then override the default gulp path by setting AppSettingGULP_PATH = D:\home\npm_tools\

Long version:

1) Go to DebugConsole above

2) npm config set prefix "D:\home\npm_tools"

(or wherever you want)



3) npm install -g gulp

(or you can actually zip the folder from your computer and drop it somewhere if your machine also works with windows)

4) Go to the portal or where you manage app settings and install GULP_PATH = D:\home\npm_tools\

5) Update DebugConsole

6) gulp -v

, you should get 3.9.0

if you just installed the latest at the time of this writing

I understand this is a bit hacky and manual, but it should unblock you until we update the gulp version

+1


source


I just tested gulp -v

on a new Azure web app. Gulp is present. Since you are experiencing difficulties, you can try installing it.



  • Switch to your-domain.scm.azurewebsites.net

  • Select Debug Console> CMD
  • Run npm install gulp

  • Testing with gulp -v

0


source







All Articles