Why don't I have a node-gyp directory?

Question

1.00/5 (1 vote)

See more:

, +

I uninstalled and reinstalled node-gyp, and when I go to the directory:

C:\Program Files\nodejs\node_modules\npm\

, there is no \node-gyp\ directory. I've also checked to see if node-gyp even exists by using the npm ls command in this directory:

C:\Program Files\nodejs\
It says that it contains node-gyp@3.6.2, so it does exist. Why isn't a node-gyp directory being created when I install node-gyp? The version of node-gyp is as stated below:

What I have tried:

C:\Program Files\nodejs>npm ls
C:\Program Files\nodejs
`-- npm@3.10.10

// Skipping down a bit

+-- node-gyp@3.4.0
 | +-- minimatch@3.0.3
 | | `-- brace-expansion@1.1.6
 | |   +-- balanced-match@0.4.2
 | |   `-- concat-map@0.0.1
 | +-- npmlog@3.1.2
 | | +-- are-we-there-yet@1.1.2
 | | | `-- delegates@1.0.0
 | | +-- console-control-strings@1.1.0
 | | +-- gauge@2.6.0
 | | | +-- has-color@0.1.7
 | | | +-- object-assign@4.1.0
 | | | +-- signal-exit@3.0.0
 | | | +-- string-width@1.0.2
 | | | | +-- code-point-at@1.0.0
 | | | | | `-- number-is-nan@1.0.0
 | | | | `-- is-fullwidth-code-point@1.0.0
 | | | |   `-- number-is-nan@1.0.0
 | | | `-- wide-align@1.1.0
 | | `-- set-blocking@2.0.0
 | `-- path-array@1.0.1
 |   `-- array-index@1.0.0
 |     +-- debug@2.2.0
 |     | `-- ms@0.7.1
 |     `-- es6-symbol@3.1.0
 |       +-- d@0.1.1
 |       `-- es5-ext@0.10.12
 |         `-- es6-iterator@2.0.0

Posted 21-Jun-17 14:44pm

fowwest

Updated 10-Jul-17 11:58am

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

_m0n · Answer 1 · 2017-07-10T11:58:00

Hi,

how are you installing node-gyp?
Have you added -g flag?

npm list -g --depth=0
do you see node-gyp?

Then, run cmd as Administrator and do:
npm uninstall node-gyp -g

then, run
npm install node-gyp -g

If it doesn't help, may be you need to clear npm cache or update node/npm itself?
To clear cache: npm cache clear --force (use with caution!)

NOTE: update npm module carefully, starting from npm version 5 there are may be breaking changes.

If you have updated node.js and npm to version 5+, you can do, as Administrator:
npm doctor -g

To see possible issues...