Installation of NPM Package is failing











up vote
2
down vote

favorite












I am trying to use Bitbuckets Pipelines to auto deploy with my commits to a test project while I practice a solid solution.



One way I have seen to do this is with "git-ftp", I am open to other NPM packages if someone knows.



Currently, when trying to install this package I get the below error



[nodegit] Everything is ready to go, attempting compilation
[nodegit] Building native node module.
{ Error: Command failed:
C:UsersprofileDocumentscompanyProjectscoming_soon-
v1node_modulesnodegitnode_modules.binnode-gyp rebuild
gyp ERR! build error
gyp ERR! stack Error: `D:VS_EnterpriseMSBuild15.0BinMSBuild.exe` failed
with exit code: 1
gyp ERR! stack at ChildProcess.onExit
(C:UsersprofileDocumentscompanyProjectscoming_soon-
v1node_modulesnodegitnode_modulesnode-gyplibbuild.js:262:23)
gyp ERR! stack at emitTwo (events.js:126:13)
gyp ERR! stack at ChildProcess.emit (events.js:214:7)
gyp ERR! stack at Process.ChildProcess._handle.onexit
(internal/child_process.js:198:12)
gyp ERR! System Windows_NT 10.0.17134
gyp ERR! command "C:\Program Files\nodejs\node.exe"
"C:\Users\profile\Documents\company\Projects\coming_soon-
v1\node_modules\nodegit\node_modules\node-gyp\bin\node-gyp.js"
"rebuild"
gyp ERR! cwd C:UsersprofileDocumentscompanyProjectscoming_soon-
v1node_modulesnodegit
gyp ERR! node -v v8.11.4
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok

at ChildProcess.exithandler (child_process.js:275:12)
at emitTwo (events.js:126:13)
at ChildProcess.emit (events.js:214:7)
at maybeClose (internal/child_process.js:925:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
killed: false,
code: 1,
signal: null,
cmd: 'C:\Users\profile\Documents\company\Projects\coming_soon-
v1\node_modules\nodegit\node_modules\.bin\node-gyp rebuild' }
undefined
npm ERR! code ELIFECYCLE
npm ERR! errno 13
npm ERR! nodegit@0.5.0 install: `node lifecycleScripts/install`
npm ERR! Exit status 13
npm ERR!
npm ERR! Failed at the nodegit@0.5.0 install script.
npm ERR! This is probably not a problem with npm. There is likely additional
logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! C:UsersprofileAppDataRoamingnpm-cache_logs2018-11-
07T04_57_44_011Z-debug.log


I have taken steps to fix this by uninstalling all versions of Python and sticking to version 2.7 as it is supposed to be the most stable. (Article online said that the newer versions don't support all node packages.)



I have also installed the Visual Studio Build Tools even though they have been installed before multiple times. I did this both from the NPM install script as well as manually.



At this point, I am unaware of what the real issue is here and I'm not the only one running into this issue, so I would like to shine a light on this issue and find a solid solution and answer to fix this.



Any and all help is greatly appreciated!



P.S If there is also another way to setup git-ftp style without using that package please do let me know and I can try that solution as well. At the end of the day, my site uses FTP to upload to our staging site, for this reason, I want to be able to auto-deploy for staging and then write another script for SSH to our production.










share|improve this question
























  • Did you check the log file: C:UsersprofileAppDataRoamingnpm-cache_logs2018-11- 07T04_57_44_011Z-debug.log
    – Eray Balkanli
    Nov 11 at 2:24















up vote
2
down vote

favorite












I am trying to use Bitbuckets Pipelines to auto deploy with my commits to a test project while I practice a solid solution.



One way I have seen to do this is with "git-ftp", I am open to other NPM packages if someone knows.



Currently, when trying to install this package I get the below error



[nodegit] Everything is ready to go, attempting compilation
[nodegit] Building native node module.
{ Error: Command failed:
C:UsersprofileDocumentscompanyProjectscoming_soon-
v1node_modulesnodegitnode_modules.binnode-gyp rebuild
gyp ERR! build error
gyp ERR! stack Error: `D:VS_EnterpriseMSBuild15.0BinMSBuild.exe` failed
with exit code: 1
gyp ERR! stack at ChildProcess.onExit
(C:UsersprofileDocumentscompanyProjectscoming_soon-
v1node_modulesnodegitnode_modulesnode-gyplibbuild.js:262:23)
gyp ERR! stack at emitTwo (events.js:126:13)
gyp ERR! stack at ChildProcess.emit (events.js:214:7)
gyp ERR! stack at Process.ChildProcess._handle.onexit
(internal/child_process.js:198:12)
gyp ERR! System Windows_NT 10.0.17134
gyp ERR! command "C:\Program Files\nodejs\node.exe"
"C:\Users\profile\Documents\company\Projects\coming_soon-
v1\node_modules\nodegit\node_modules\node-gyp\bin\node-gyp.js"
"rebuild"
gyp ERR! cwd C:UsersprofileDocumentscompanyProjectscoming_soon-
v1node_modulesnodegit
gyp ERR! node -v v8.11.4
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok

at ChildProcess.exithandler (child_process.js:275:12)
at emitTwo (events.js:126:13)
at ChildProcess.emit (events.js:214:7)
at maybeClose (internal/child_process.js:925:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
killed: false,
code: 1,
signal: null,
cmd: 'C:\Users\profile\Documents\company\Projects\coming_soon-
v1\node_modules\nodegit\node_modules\.bin\node-gyp rebuild' }
undefined
npm ERR! code ELIFECYCLE
npm ERR! errno 13
npm ERR! nodegit@0.5.0 install: `node lifecycleScripts/install`
npm ERR! Exit status 13
npm ERR!
npm ERR! Failed at the nodegit@0.5.0 install script.
npm ERR! This is probably not a problem with npm. There is likely additional
logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! C:UsersprofileAppDataRoamingnpm-cache_logs2018-11-
07T04_57_44_011Z-debug.log


I have taken steps to fix this by uninstalling all versions of Python and sticking to version 2.7 as it is supposed to be the most stable. (Article online said that the newer versions don't support all node packages.)



I have also installed the Visual Studio Build Tools even though they have been installed before multiple times. I did this both from the NPM install script as well as manually.



At this point, I am unaware of what the real issue is here and I'm not the only one running into this issue, so I would like to shine a light on this issue and find a solid solution and answer to fix this.



Any and all help is greatly appreciated!



P.S If there is also another way to setup git-ftp style without using that package please do let me know and I can try that solution as well. At the end of the day, my site uses FTP to upload to our staging site, for this reason, I want to be able to auto-deploy for staging and then write another script for SSH to our production.










share|improve this question
























  • Did you check the log file: C:UsersprofileAppDataRoamingnpm-cache_logs2018-11- 07T04_57_44_011Z-debug.log
    – Eray Balkanli
    Nov 11 at 2:24













up vote
2
down vote

favorite









up vote
2
down vote

favorite











I am trying to use Bitbuckets Pipelines to auto deploy with my commits to a test project while I practice a solid solution.



One way I have seen to do this is with "git-ftp", I am open to other NPM packages if someone knows.



Currently, when trying to install this package I get the below error



[nodegit] Everything is ready to go, attempting compilation
[nodegit] Building native node module.
{ Error: Command failed:
C:UsersprofileDocumentscompanyProjectscoming_soon-
v1node_modulesnodegitnode_modules.binnode-gyp rebuild
gyp ERR! build error
gyp ERR! stack Error: `D:VS_EnterpriseMSBuild15.0BinMSBuild.exe` failed
with exit code: 1
gyp ERR! stack at ChildProcess.onExit
(C:UsersprofileDocumentscompanyProjectscoming_soon-
v1node_modulesnodegitnode_modulesnode-gyplibbuild.js:262:23)
gyp ERR! stack at emitTwo (events.js:126:13)
gyp ERR! stack at ChildProcess.emit (events.js:214:7)
gyp ERR! stack at Process.ChildProcess._handle.onexit
(internal/child_process.js:198:12)
gyp ERR! System Windows_NT 10.0.17134
gyp ERR! command "C:\Program Files\nodejs\node.exe"
"C:\Users\profile\Documents\company\Projects\coming_soon-
v1\node_modules\nodegit\node_modules\node-gyp\bin\node-gyp.js"
"rebuild"
gyp ERR! cwd C:UsersprofileDocumentscompanyProjectscoming_soon-
v1node_modulesnodegit
gyp ERR! node -v v8.11.4
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok

at ChildProcess.exithandler (child_process.js:275:12)
at emitTwo (events.js:126:13)
at ChildProcess.emit (events.js:214:7)
at maybeClose (internal/child_process.js:925:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
killed: false,
code: 1,
signal: null,
cmd: 'C:\Users\profile\Documents\company\Projects\coming_soon-
v1\node_modules\nodegit\node_modules\.bin\node-gyp rebuild' }
undefined
npm ERR! code ELIFECYCLE
npm ERR! errno 13
npm ERR! nodegit@0.5.0 install: `node lifecycleScripts/install`
npm ERR! Exit status 13
npm ERR!
npm ERR! Failed at the nodegit@0.5.0 install script.
npm ERR! This is probably not a problem with npm. There is likely additional
logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! C:UsersprofileAppDataRoamingnpm-cache_logs2018-11-
07T04_57_44_011Z-debug.log


I have taken steps to fix this by uninstalling all versions of Python and sticking to version 2.7 as it is supposed to be the most stable. (Article online said that the newer versions don't support all node packages.)



I have also installed the Visual Studio Build Tools even though they have been installed before multiple times. I did this both from the NPM install script as well as manually.



At this point, I am unaware of what the real issue is here and I'm not the only one running into this issue, so I would like to shine a light on this issue and find a solid solution and answer to fix this.



Any and all help is greatly appreciated!



P.S If there is also another way to setup git-ftp style without using that package please do let me know and I can try that solution as well. At the end of the day, my site uses FTP to upload to our staging site, for this reason, I want to be able to auto-deploy for staging and then write another script for SSH to our production.










share|improve this question















I am trying to use Bitbuckets Pipelines to auto deploy with my commits to a test project while I practice a solid solution.



One way I have seen to do this is with "git-ftp", I am open to other NPM packages if someone knows.



Currently, when trying to install this package I get the below error



[nodegit] Everything is ready to go, attempting compilation
[nodegit] Building native node module.
{ Error: Command failed:
C:UsersprofileDocumentscompanyProjectscoming_soon-
v1node_modulesnodegitnode_modules.binnode-gyp rebuild
gyp ERR! build error
gyp ERR! stack Error: `D:VS_EnterpriseMSBuild15.0BinMSBuild.exe` failed
with exit code: 1
gyp ERR! stack at ChildProcess.onExit
(C:UsersprofileDocumentscompanyProjectscoming_soon-
v1node_modulesnodegitnode_modulesnode-gyplibbuild.js:262:23)
gyp ERR! stack at emitTwo (events.js:126:13)
gyp ERR! stack at ChildProcess.emit (events.js:214:7)
gyp ERR! stack at Process.ChildProcess._handle.onexit
(internal/child_process.js:198:12)
gyp ERR! System Windows_NT 10.0.17134
gyp ERR! command "C:\Program Files\nodejs\node.exe"
"C:\Users\profile\Documents\company\Projects\coming_soon-
v1\node_modules\nodegit\node_modules\node-gyp\bin\node-gyp.js"
"rebuild"
gyp ERR! cwd C:UsersprofileDocumentscompanyProjectscoming_soon-
v1node_modulesnodegit
gyp ERR! node -v v8.11.4
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok

at ChildProcess.exithandler (child_process.js:275:12)
at emitTwo (events.js:126:13)
at ChildProcess.emit (events.js:214:7)
at maybeClose (internal/child_process.js:925:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
killed: false,
code: 1,
signal: null,
cmd: 'C:\Users\profile\Documents\company\Projects\coming_soon-
v1\node_modules\nodegit\node_modules\.bin\node-gyp rebuild' }
undefined
npm ERR! code ELIFECYCLE
npm ERR! errno 13
npm ERR! nodegit@0.5.0 install: `node lifecycleScripts/install`
npm ERR! Exit status 13
npm ERR!
npm ERR! Failed at the nodegit@0.5.0 install script.
npm ERR! This is probably not a problem with npm. There is likely additional
logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! C:UsersprofileAppDataRoamingnpm-cache_logs2018-11-
07T04_57_44_011Z-debug.log


I have taken steps to fix this by uninstalling all versions of Python and sticking to version 2.7 as it is supposed to be the most stable. (Article online said that the newer versions don't support all node packages.)



I have also installed the Visual Studio Build Tools even though they have been installed before multiple times. I did this both from the NPM install script as well as manually.



At this point, I am unaware of what the real issue is here and I'm not the only one running into this issue, so I would like to shine a light on this issue and find a solid solution and answer to fix this.



Any and all help is greatly appreciated!



P.S If there is also another way to setup git-ftp style without using that package please do let me know and I can try that solution as well. At the end of the day, my site uses FTP to upload to our staging site, for this reason, I want to be able to auto-deploy for staging and then write another script for SSH to our production.







npm deployment npm-install






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 7 at 10:38









kostix

29.9k647102




29.9k647102










asked Nov 7 at 5:09









Keeano

126627




126627












  • Did you check the log file: C:UsersprofileAppDataRoamingnpm-cache_logs2018-11- 07T04_57_44_011Z-debug.log
    – Eray Balkanli
    Nov 11 at 2:24


















  • Did you check the log file: C:UsersprofileAppDataRoamingnpm-cache_logs2018-11- 07T04_57_44_011Z-debug.log
    – Eray Balkanli
    Nov 11 at 2:24
















Did you check the log file: C:UsersprofileAppDataRoamingnpm-cache_logs2018-11- 07T04_57_44_011Z-debug.log
– Eray Balkanli
Nov 11 at 2:24




Did you check the log file: C:UsersprofileAppDataRoamingnpm-cache_logs2018-11- 07T04_57_44_011Z-debug.log
– Eray Balkanli
Nov 11 at 2:24












1 Answer
1






active

oldest

votes

















up vote
2
down vote



accepted
+50










The error you're getting is coming from node-gyp which is failing to complile nodegit. There's an issue on the nodegit github page that might help: "I got an error when i npm install in nodegit on windows10"



On an unrelated note, you mentioned that you're using the git-ftp node package. This package has only one release, version v0.0.0, and hasn't been updated for 3 years. You'll probably be better off steering clear of that package. The issue you're getting also stems from the fact that git-ftp depends on nodegit.






share|improve this answer





















  • Good point, I ended up going the Docker route in the end but I should learn to check the status of these repositories as well.
    – Keeano
    Nov 17 at 20:27











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53183869%2finstallation-of-npm-package-is-failing%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
2
down vote



accepted
+50










The error you're getting is coming from node-gyp which is failing to complile nodegit. There's an issue on the nodegit github page that might help: "I got an error when i npm install in nodegit on windows10"



On an unrelated note, you mentioned that you're using the git-ftp node package. This package has only one release, version v0.0.0, and hasn't been updated for 3 years. You'll probably be better off steering clear of that package. The issue you're getting also stems from the fact that git-ftp depends on nodegit.






share|improve this answer





















  • Good point, I ended up going the Docker route in the end but I should learn to check the status of these repositories as well.
    – Keeano
    Nov 17 at 20:27















up vote
2
down vote



accepted
+50










The error you're getting is coming from node-gyp which is failing to complile nodegit. There's an issue on the nodegit github page that might help: "I got an error when i npm install in nodegit on windows10"



On an unrelated note, you mentioned that you're using the git-ftp node package. This package has only one release, version v0.0.0, and hasn't been updated for 3 years. You'll probably be better off steering clear of that package. The issue you're getting also stems from the fact that git-ftp depends on nodegit.






share|improve this answer





















  • Good point, I ended up going the Docker route in the end but I should learn to check the status of these repositories as well.
    – Keeano
    Nov 17 at 20:27













up vote
2
down vote



accepted
+50







up vote
2
down vote



accepted
+50




+50




The error you're getting is coming from node-gyp which is failing to complile nodegit. There's an issue on the nodegit github page that might help: "I got an error when i npm install in nodegit on windows10"



On an unrelated note, you mentioned that you're using the git-ftp node package. This package has only one release, version v0.0.0, and hasn't been updated for 3 years. You'll probably be better off steering clear of that package. The issue you're getting also stems from the fact that git-ftp depends on nodegit.






share|improve this answer












The error you're getting is coming from node-gyp which is failing to complile nodegit. There's an issue on the nodegit github page that might help: "I got an error when i npm install in nodegit on windows10"



On an unrelated note, you mentioned that you're using the git-ftp node package. This package has only one release, version v0.0.0, and hasn't been updated for 3 years. You'll probably be better off steering clear of that package. The issue you're getting also stems from the fact that git-ftp depends on nodegit.







share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 16 at 13:02









Nico

2,1301224




2,1301224












  • Good point, I ended up going the Docker route in the end but I should learn to check the status of these repositories as well.
    – Keeano
    Nov 17 at 20:27


















  • Good point, I ended up going the Docker route in the end but I should learn to check the status of these repositories as well.
    – Keeano
    Nov 17 at 20:27
















Good point, I ended up going the Docker route in the end but I should learn to check the status of these repositories as well.
– Keeano
Nov 17 at 20:27




Good point, I ended up going the Docker route in the end but I should learn to check the status of these repositories as well.
– Keeano
Nov 17 at 20:27


















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53183869%2finstallation-of-npm-package-is-failing%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Schultheiß

Verwaltungsgliederung Dänemarks

Liste der Kulturdenkmale in Wilsdruff