MSBuild.NodeTools
MSBuild.NodeTools copied to clipboard
Gulp module not found.
Hi there, I have installed MSBuild.Node and MSBuild.Gulp. After intalling additional Nugets "Node.js" and "Npm" - msbuild was able to execute "npm install".
But my Gulp target still gets this error:
packages\MSBuild.Gulp.0.5.1\build\MSBuild.Gulp.targets(20):packages\MSBuild.Gulp.0.5.1\
build\MSBuild.Gulp.targets(20,9):
Error : 'Gulp module not found. Please install Gulp in the node module path
'C:\b\2\s\packages\Node.js.5.3.0'.'
--
Process 'msbuild.exe' exited with code '1'.
Gulp is alredy installed locally via npm.
Any ideas or am I complety on a wrong path?
I'm having a similar issue with dotnet publish
. Annoyingly, it works from my Gitlab CI pipeline, but not if I run it as myself from the build server.
C:\Users\derbro\.nuget\packages\msbuild.gulp\0.5.1\build\MSBuild.Gulp.targets(20,9): error : 'Gulp module not found. Please install Gulp in the node module path
'C:\Users\derbro\AppData\Roaming\npm'.' [C:\gitlab-runner\builds\b0800511\0\console\uk.ac.sahfos.cpr.console.web\uk.ac.sahfos.cpr.console.web\uk.ac.sahfos.cpr.console.web.csproj]
I'm seriously considering just copying the ...\Appdata\Roaming\npm
folder from the one used by the gitlab pipelines.
A year later, a new system, and I'm having it again! I never did solve it, I just stopped trying to run it as myself on the Build server.
@auspex sorry to revive a bit of a necro, but I've resolved this by adding a property group to the .csproj file, like so:
<PropertyGroup><NpmCommand>install -g gulp</NpmCommand></PropertyGroup>