Problem with installing "npm install -g learnyournode" on my Windows PC

Problem with installing "npm install -g learnyournode" on my Windows PC
0

#1

Hello folks!
I am learning Back End Programming using freecodecamp. I cannot create a c9.io account because I can’t get anyone give their credit/debit card info :stuck_out_tongue:

Figuring out the solution, I have installed node js on my own personal computer and I completed the first Challenge “Managing and installing npm packages”. But for second challenge, I cannot install the learnyournode package. It gives me error like this: (screenshot)

How do I fix this? please note that I have copy-pasted the install command, so no chance of wrong command.

Thanks!

Just in case, I have installed github on pc. But I dunno what’s up with this git error duh…


#2

I haven’t been able to find a solution to your problem based on this information.
What version of Windows do you have? What’s the version of npm you’re using?
Can you post the complete log?

Also, while we’re on the topic of learnyounode, I’ll have to warn you that I found a lot of the lessons very poorly explained, so you might want to look into alternatives.


#3

@Zekany
OS: Windows 10 Pro (32 bit Operating System)
npm Version: 5.3.0

Complete Log:

0 info it worked if it ends with ok
1 verbose cli [ ‘C:\Program Files\nodejs\node.exe’,
1 verbose cli ‘C:\Users\SRUJAN\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js’,
1 verbose cli ‘install’,
1 verbose cli ‘-g’,
1 verbose cli ‘learnyounode’ ]
2 info using npm@5.3.0
3 info using node@v6.10.2
4 verbose npm-session 928e5d70f032fc8e
5 silly install loadCurrentTree
6 silly install readGlobalPackageData
7 http fetch GET 304 https://registry.npmjs.org/learnyounode 925ms (from cache)
8 silly pacote tag manifest for learnyounode@latest fetched in 1064ms
9 silly install loadIdealTree
10 silly install cloneCurrentTreeToIdealTree
11 silly install loadShrinkwrap
12 silly install loadAllDepsIntoIdealTree
13 silly resolveWithNewModule learnyounode@3.5.10 checking installable status
14 http fetch GET 304 https://registry.npmjs.org/after 344ms (from cache)
15 silly pacote range manifest for after@~0.8.1 fetched in 453ms
16 silly resolveWithNewModule after@0.8.2 checking installable status
17 http fetch GET 304 https://registry.npmjs.org/through2 224ms (from cache)
18 silly pacote range manifest for through2@^2.0.1 fetched in 297ms
19 silly resolveWithNewModule through2@2.0.3 checking installable status
20 http fetch GET 304 https://registry.npmjs.org/concat-stream 937ms (from cache)
21 http fetch GET 304 https://registry.npmjs.org/duplexer 969ms (from cache)
22 http fetch GET 304 https://registry.npmjs.org/colors-tmpl 1015ms (from cache)
23 http fetch GET 304 https://registry.npmjs.org/combined-stream 984ms (from cache)
24 silly pacote range manifest for concat-stream@^1.5.1 fetched in 1000ms
25 silly resolveWithNewModule concat-stream@1.6.0 checking installable status
26 http fetch GET 304 https://registry.npmjs.org/bl 1046ms (from cache)
27 http fetch GET 304 https://registry.npmjs.org/hyperquest 1005ms (from cache)
28 http fetch GET 304 https://registry.npmjs.org/rimraf 1034ms (from cache)
29 http fetch GET 304 https://registry.npmjs.org/through 1047ms (from cache)
30 silly pacote range manifest for duplexer@^0.1.1 fetched in 1094ms
31 silly resolveWithNewModule duplexer@0.1.1 checking installable status
32 silly pacote range manifest for colors-tmpl@^1.0.0 fetched in 1125ms
33 silly resolveWithNewModule colors-tmpl@1.0.0 checking installable status
34 silly pacote range manifest for combined-stream@^1.0.5 fetched in 1109ms
35 silly resolveWithNewModule combined-stream@1.0.5 checking installable status
36 silly pacote range manifest for hyperquest@^2.0.0 fetched in 1083ms
37 silly resolveWithNewModule hyperquest@2.1.2 checking installable status
38 silly pacote range manifest for bl@^1.1.2 fetched in 1171ms
39 silly resolveWithNewModule bl@1.2.1 checking installable status
40 silly pacote range manifest for rimraf@^2.5.4 fetched in 1128ms
41 silly resolveWithNewModule rimraf@2.6.1 checking installable status
42 silly pacote range manifest for through@^2.3.8 fetched in 1125ms
43 silly resolveWithNewModule through@2.3.8 checking installable status
44 http fetch GET 304 https://registry.npmjs.org/boganipsum 1187ms (from cache)
45 http fetch GET 304 https://registry.npmjs.org/through2-map 500ms (from cache)
46 silly pacote range manifest for boganipsum@~0.1.0 fetched in 1234ms
47 silly resolveWithNewModule boganipsum@0.1.0 checking installable status
48 silly pacote range manifest for through2-map@^3.0.0 fetched in 522ms
49 silly resolveWithNewModule through2-map@3.0.0 checking installable status
50 http fetch GET 304 https://registry.npmjs.org/workshopper-adventure 344ms (from cache)
51 silly pacote range manifest for workshopper-adventure@^6.0.0 fetched in 391ms
52 silly resolveWithNewModule workshopper-adventure@6.0.2 checking installable status
53 http fetch GET 304 https://registry.npmjs.org/workshopper-wrappedexec 318ms (from cache)
54 silly pacote range manifest for workshopper-wrappedexec@~0.1.1 fetched in 343ms
55 silly resolveWithNewModule workshopper-wrappedexec@0.1.3 checking installable status
56 http fetch GET 304 https://registry.npmjs.org/workshopper-exercise 359ms (from cache)
57 silly pacote range manifest for workshopper-exercise@^3.0.1 fetched in 439ms
58 silly resolveWithNewModule workshopper-exercise@3.0.1 checking installable status
59 http fetch GET 304 https://registry.npmjs.org/readable-stream 326ms (from cache)
60 silly pacote range manifest for readable-stream@^2.0.5 fetched in 357ms
61 silly resolveWithNewModule readable-stream@2.3.3 checking installable status
62 http fetch GET 304 https://registry.npmjs.org/isarray 375ms (from cache)
63 silly pacote range manifest for isarray@~1.0.0 fetched in 423ms
64 silly resolveWithNewModule isarray@1.0.0 checking installable status
65 http fetch GET 304 https://registry.npmjs.org/process-nextick-args 412ms (from cache)
66 http fetch GET 304 https://registry.npmjs.org/core-util-is 428ms (from cache)
67 http fetch GET 304 https://registry.npmjs.org/string_decoder 433ms (from cache)
68 http fetch GET 304 https://registry.npmjs.org/safe-buffer 435ms (from cache)
69 http fetch GET 304 https://registry.npmjs.org/util-deprecate 433ms (from cache)
70 silly pacote range manifest for process-nextick-args@~1.0.6 fetched in 479ms
71 silly resolveWithNewModule process-nextick-args@1.0.7 checking installable status
72 silly pacote range manifest for safe-buffer@~5.1.1 fetched in 482ms
73 silly resolveWithNewModule safe-buffer@5.1.1 checking installable status
74 silly pacote range manifest for util-deprecate@~1.0.1 fetched in 480ms
75 silly resolveWithNewModule util-deprecate@1.0.2 checking installable status
76 silly pacote range manifest for string_decoder@~1.0.3 fetched in 480ms
77 silly resolveWithNewModule string_decoder@1.0.3 checking installable status
78 http fetch GET 304 https://registry.npmjs.org/inherits 519ms (from cache)
79 silly pacote range manifest for inherits@~2.0.3 fetched in 531ms
80 silly resolveWithNewModule inherits@2.0.3 checking installable status
81 silly pacote range manifest for core-util-is@~1.0.0 fetched in 563ms
82 silly resolveWithNewModule core-util-is@1.0.2 checking installable status
83 http fetch GET 304 https://registry.npmjs.org/colors 235ms (from cache)
84 silly pacote range manifest for colors@~1.0.2 fetched in 281ms
85 silly resolveWithNewModule colors@1.0.3 checking installable status
86 http fetch GET 304 https://registry.npmjs.org/delayed-stream 312ms (from cache)
87 silly pacote range manifest for delayed-stream@~1.0.0 fetched in 344ms
88 silly resolveWithNewModule delayed-stream@1.0.0 checking installable status
89 http fetch GET 304 https://registry.npmjs.org/typedarray 221ms (from cache)
90 silly pacote range manifest for typedarray@^0.0.6 fetched in 235ms
91 silly resolveWithNewModule typedarray@0.0.6 checking installable status
92 silly pacote range manifest for through2@~0.6.3 fetched in 60ms
93 silly resolveWithNewModule through2@0.6.5 checking installable status
94 http fetch GET 304 https://registry.npmjs.org/buffer-from 250ms (from cache)
95 silly pacote range manifest for buffer-from@^0.1.1 fetched in 281ms
96 silly resolveWithNewModule buffer-from@0.1.1 checking installable status
97 http fetch GET 304 https://registry.npmjs.org/duplexer2 265ms (from cache)
98 silly pacote range manifest for duplexer2@~0.0.2 fetched in 297ms
99 silly resolveWithNewModule duplexer2@0.0.2 checking installable status
100 http fetch GET 304 https://registry.npmjs.org/is-array-buffer-x 219ms (from cache)
101 silly pacote range manifest for is-array-buffer-x@^1.0.13 fetched in 250ms
102 silly resolveWithNewModule is-array-buffer-x@1.3.0 checking installable status
103 http fetch GET 304 https://registry.npmjs.org/is-object-like-x 266ms (from cache)
104 http fetch GET 304 https://registry.npmjs.org/has-to-string-tag-x 281ms (from cache)
105 http fetch GET 304 https://registry.npmjs.org/to-string-tag-x 281ms (from cache)
106 silly pacote range manifest for is-object-like-x@^1.3.0 fetched in 313ms
107 silly resolveWithNewModule is-object-like-x@1.5.0 checking installable status
108 silly pacote range manifest for has-to-string-tag-x@^1.4.0 fetched in 313ms
109 silly resolveWithNewModule has-to-string-tag-x@1.4.0 checking installable status
110 silly pacote range manifest for to-string-tag-x@^1.4.0 fetched in 329ms
111 silly resolveWithNewModule to-string-tag-x@1.4.0 checking installable status
112 http fetch GET 304 https://registry.npmjs.org/has-symbol-support-x 274ms (from cache)
113 silly pacote range manifest for has-symbol-support-x@^1.4.0 fetched in 292ms
114 silly resolveWithNewModule has-symbol-support-x@1.4.0 checking installable status
115 http fetch GET 304 https://registry.npmjs.org/is-primitive 214ms (from cache)
116 silly pacote range manifest for is-primitive@^2.0.0 fetched in 245ms
117 silly resolveWithNewModule is-primitive@2.0.0 checking installable status
118 http fetch GET 304 https://registry.npmjs.org/is-function-x 245ms (from cache)
119 silly pacote range manifest for is-function-x@^3.1.0 fetched in 261ms
120 silly resolveWithNewModule is-function-x@3.1.0 checking installable status
121 http fetch GET 304 https://registry.npmjs.org/normalize-space-x 250ms (from cache)
122 http fetch GET 304 https://registry.npmjs.org/replace-comments-x 250ms (from cache)
123 silly pacote range manifest for replace-comments-x@^1.0.1 fetched in 266ms
124 silly resolveWithNewModule replace-comments-x@1.0.1 checking installable status
125 silly pacote range manifest for normalize-space-x@^1.3.2 fetched in 319ms
126 silly resolveWithNewModule normalize-space-x@1.3.2 checking installable status
127 http fetch GET 304 https://registry.npmjs.org/white-space-x 296ms (from cache)
128 silly pacote range manifest for white-space-x@^2.0.2 fetched in 317ms
129 silly resolveWithNewModule white-space-x@2.0.2 checking installable status
130 http fetch GET 304 https://registry.npmjs.org/trim-x 801ms (from cache)
131 silly pacote range manifest for trim-x@^1.0.2 fetched in 817ms
132 silly resolveWithNewModule trim-x@1.0.2 checking installable status
133 http fetch GET 304 https://registry.npmjs.org/trim-left-x 234ms (from cache)
134 http fetch GET 304 https://registry.npmjs.org/trim-right-x 250ms (from cache)
135 silly pacote range manifest for trim-left-x@^1.3.3 fetched in 250ms
136 silly resolveWithNewModule trim-left-x@1.3.3 checking installable status
137 silly pacote range manifest for trim-right-x@^1.3.2 fetched in 266ms
138 silly resolveWithNewModule trim-right-x@1.3.2 checking installable status
139 http fetch GET 304 https://registry.npmjs.org/to-string-x 219ms (from cache)
140 silly pacote range manifest for to-string-x@^1.4.0 fetched in 313ms
141 silly resolveWithNewModule to-string-x@1.4.0 checking installable status
142 http fetch GET 304 https://registry.npmjs.org/is-symbol 259ms (from cache)
143 silly pacote range manifest for is-symbol@^1.0.1 fetched in 274ms
144 silly resolveWithNewModule is-symbol@1.0.1 checking installable status
145 http fetch GET 304 https://registry.npmjs.org/is-string 200ms (from cache)
146 silly pacote range manifest for is-string@^1.0.4 fetched in 334ms
147 silly resolveWithNewModule is-string@1.0.4 checking installable status
148 http fetch GET 304 https://registry.npmjs.org/validate.io-undefined 234ms (from cache)
149 http fetch GET 304 https://registry.npmjs.org/lodash.isnull 234ms (from cache)
150 silly pacote range manifest for validate.io-undefined@^1.0.3 fetched in 267ms
151 silly resolveWithNewModule validate.io-undefined@1.0.3 checking installable status
152 silly pacote range manifest for lodash.isnull@^3.0.0 fetched in 267ms
153 silly resolveWithNewModule lodash.isnull@3.0.0 checking installable status
154 silly pacote range manifest for readable-stream@~1.1.9 fetched in 45ms
155 silly resolveWithNewModule readable-stream@1.1.14 checking installable status
156 silly pacote range manifest for string_decoder@~0.10.x fetched in 16ms
157 silly resolveWithNewModule string_decoder@0.10.31 checking installable status
158 silly pacote version manifest for isarray@0.0.1 fetched in 16ms
159 silly resolveWithNewModule isarray@0.0.1 checking installable status
160 silly pacote range manifest for readable-stream@>=1.0.33-1 <1.1.0-0 fetched in 43ms
161 silly resolveWithNewModule readable-stream@1.0.34 checking installable status
162 http fetch GET 304 https://registry.npmjs.org/xtend 231ms (from cache)
163 silly pacote range manifest for xtend@>=4.0.0 <4.1.0-0 fetched in 246ms
164 silly resolveWithNewModule xtend@4.0.1 checking installable status
165 silly pacote version manifest for isarray@0.0.1 fetched in 15ms
166 silly resolveWithNewModule isarray@0.0.1 checking installable status
167 silly pacote range manifest for string_decoder@~0.10.x fetched in 15ms
168 silly resolveWithNewModule string_decoder@0.10.31 checking installable status
169 http fetch GET 304 https://registry.npmjs.org/glob 204ms (from cache)
170 silly pacote range manifest for glob@^7.0.5 fetched in 227ms
171 silly resolveWithNewModule glob@7.1.2 checking installable status
172 http fetch GET 304 https://registry.npmjs.org/inflight 407ms (from cache)
173 http fetch GET 304 https://registry.npmjs.org/path-is-absolute 407ms (from cache)
174 http fetch GET 304 https://registry.npmjs.org/minimatch 407ms (from cache)
175 http fetch GET 304 https://registry.npmjs.org/fs.realpath 422ms (from cache)
176 silly pacote range manifest for inflight@^1.0.4 fetched in 438ms
177 silly resolveWithNewModule inflight@1.0.6 checking installable status
178 http fetch GET 304 https://registry.npmjs.org/once 438ms (from cache)
179 silly pacote range manifest for minimatch@^3.0.4 fetched in 454ms
180 silly resolveWithNewModule minimatch@3.0.4 checking installable status
181 silly pacote range manifest for path-is-absolute@^1.0.0 fetched in 473ms
182 silly resolveWithNewModule path-is-absolute@1.0.1 checking installable status
183 silly pacote range manifest for fs.realpath@^1.0.0 fetched in 476ms
184 silly resolveWithNewModule fs.realpath@1.0.0 checking installable status
185 silly pacote range manifest for once@^1.3.0 fetched in 478ms
186 silly resolveWithNewModule once@1.4.0 checking installable status
187 http fetch GET 304 https://registry.npmjs.org/wrappy 203ms (from cache)
188 silly pacote range manifest for wrappy@1 fetched in 219ms
189 silly resolveWithNewModule wrappy@1.0.2 checking installable status
190 http fetch GET 304 https://registry.npmjs.org/brace-expansion 203ms (from cache)
191 silly pacote range manifest for brace-expansion@^1.1.7 fetched in 234ms
192 silly resolveWithNewModule brace-expansion@1.1.8 checking installable status
193 http fetch GET 304 https://registry.npmjs.org/balanced-match 224ms (from cache)
194 http fetch GET 304 https://registry.npmjs.org/concat-map 234ms (from cache)
195 silly pacote range manifest for balanced-match@^1.0.0 fetched in 250ms
196 silly resolveWithNewModule balanced-match@1.0.0 checking installable status
197 silly pacote version manifest for concat-map@0.0.1 fetched in 265ms
198 silly resolveWithNewModule concat-map@0.0.1 checking installable status
199 http fetch GET 304 https://registry.npmjs.org/latest-version 311ms (from cache)
200 silly pacote range manifest for latest-version@^3.0.0 fetched in 390ms
201 silly resolveWithNewModule latest-version@3.1.0 checking installable status
202 http fetch GET 304 https://registry.npmjs.org/commandico 547ms (from cache)
203 http fetch GET 304 https://registry.npmjs.org/combined-stream-wait-for-it 579ms (from cache)
204 http fetch GET 304 https://registry.npmjs.org/chalk 594ms (from cache)
205 http fetch GET 304 https://registry.npmjs.org/simple-terminal-menu 568ms (from cache)
206 http fetch GET 304 https://registry.npmjs.org/i18n-core 586ms (from cache)
207 http fetch GET 304 https://registry.npmjs.org/split 583ms (from cache)
208 http fetch GET 304 https://registry.npmjs.org/string-to-stream 600ms (from cache)
209 http fetch GET 304 https://registry.npmjs.org/msee 604ms (from cache)
210 http fetch GET 304 https://registry.npmjs.org/workshopper-adventure-storage 597ms (from cache)
211 silly pacote range manifest for commandico@^2.0.2 fetched in 672ms
212 silly resolveWithNewModule commandico@2.0.2 checking installable status
213 silly pacote range manifest for combined-stream-wait-for-it@^1.1.0 fetched in 672ms
214 silly resolveWithNewModule combined-stream-wait-for-it@1.1.0 checking installable status
215 silly pacote range manifest for chalk@^1.1.3 fetched in 672ms
216 silly resolveWithNewModule chalk@1.1.3 checking installable status
217 silly pacote range manifest for string-to-stream@^1.1.0 fetched in 661ms
218 silly resolveWithNewModule string-to-stream@1.1.0 checking installable status
219 silly pacote range manifest for split@^1.0.0 fetched in 662ms
220 silly resolveWithNewModule split@1.0.1 checking installable status
221 silly pacote range manifest for i18n-core@^3.0.0 fetched in 685ms
222 silly resolveWithNewModule i18n-core@3.2.0 checking installable status
223 silly fetchPackageMetaData error for codeclimate-test-reporter@github:codeclimate/javascript-test-reporter#97f1ff2cf18cd5f03191d3d53e671c47e954f2fa No git binary found in $PATH
224 silly pacote range manifest for simple-terminal-menu@^1.1.3 fetched in 818ms
225 silly resolveWithNewModule simple-terminal-menu@1.1.3 checking installable status
226 silly pacote range manifest for workshopper-adventure-storage@^3.0.0 fetched in 815ms
227 silly resolveWithNewModule workshopper-adventure-storage@3.0.0 checking installable status
228 silly pacote range manifest for msee@^0.3.2 fetched in 819ms
229 silly resolveWithNewModule msee@0.3.3 checking installable status
230 verbose stack Error: No git binary found in $PATH
230 verbose stack at checkGit (C:\Users\SRUJAN\AppData\Roaming\npm\node_modules\npm\node_modules\pacote\lib\util\git.js:197:17)
230 verbose stack at spawnGit (C:\Users\SRUJAN\AppData\Roaming\npm\node_modules\npm\node_modules\pacote\lib\util\git.js:176:10)
230 verbose stack at pinflight (C:\Users\SRUJAN\AppData\Roaming\npm\node_modules\npm\node_modules\pacote\lib\util\git.js:108:12)
230 verbose stack at C:\Users\SRUJAN\AppData\Roaming\npm\node_modules\npm\node_modules\promise-inflight\inflight.js:29:24
230 verbose stack at Promise._execute (C:\Users\SRUJAN\AppData\Roaming\npm\node_modules\npm\node_modules\bluebird\js\release\debuggability.js:300:9)
230 verbose stack at Promise._resolveFromExecutor (C:\Users\SRUJAN\AppData\Roaming\npm\node_modules\npm\node_modules\bluebird\js\release\promise.js:483:18)
230 verbose stack at new Promise (C:\Users\SRUJAN\AppData\Roaming\npm\node_modules\npm\node_modules\bluebird\js\release\promise.js:79:10)
230 verbose stack at _inflight (C:\Users\SRUJAN\AppData\Roaming\npm\node_modules\npm\node_modules\promise-inflight\inflight.js:28:25)
230 verbose stack at C:\Users\SRUJAN\AppData\Roaming\npm\node_modules\npm\node_modules\promise-inflight\inflight.js:22:14
230 verbose stack at tryCatcher (C:\Users\SRUJAN\AppData\Roaming\npm\node_modules\npm\node_modules\bluebird\js\release\util.js:16:23)
230 verbose stack at Promise._settlePromiseFromHandler (C:\Users\SRUJAN\AppData\Roaming\npm\node_modules\npm\node_modules\bluebird\js\release\promise.js:512:31)
230 verbose stack at Promise._settlePromise (C:\Users\SRUJAN\AppData\Roaming\npm\node_modules\npm\node_modules\bluebird\js\release\promise.js:569:18)
230 verbose stack at Promise._settlePromiseCtx (C:\Users\SRUJAN\AppData\Roaming\npm\node_modules\npm\node_modules\bluebird\js\release\promise.js:606:10)
230 verbose stack at Async._drainQueue (C:\Users\SRUJAN\AppData\Roaming\npm\node_modules\npm\node_modules\bluebird\js\release\async.js:138:12)
230 verbose stack at Async._drainQueues (C:\Users\SRUJAN\AppData\Roaming\npm\node_modules\npm\node_modules\bluebird\js\release\async.js:143:10)
230 verbose stack at Immediate.Async.drainQueues (C:\Users\SRUJAN\AppData\Roaming\npm\node_modules\npm\node_modules\bluebird\js\release\async.js:17:14)
231 verbose cwd C:\Users\SRUJAN
232 verbose Windows_NT 10.0.14393
233 verbose argv “C:\Program Files\nodejs\node.exe” “C:\Users\SRUJAN\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js” “install” “-g” "learnyounode"
234 verbose node v6.10.2
235 verbose npm v5.3.0
236 error code ENOGIT
237 error No git binary found in $PATH
238 error Failed using git.
238 error Please check if you have git installed and in your PATH.
239 verbose exit [ 1, true ]

I am guessing some files called “git” aren’t at a location they are supposed to be. If someone could let me know what are they, and how to put them, we could fix this problem…


#4

I had this problem when I installed Python … its in the error message that git is not installed to your path. I just reinstalled and made sure to choose the option to install to path.

Heres another way I guess of doing it too that I found on StackOverflow https://stackoverflow.com/questions/26620312/installing-git-in-path-with-github-client-for-windows


#5

It looks like you need to add the location of the git executable to your PATH variable. This is often a missed step when installing programs to Windows that you plan to call from the command line.


ETA: You can easily find out how to do this via The Great And Powerful Google, but on most Windows versions (I haven’t used 10 much yet) it’s going to be along the lines of –
My Computer > Properties > Advanced > Path > Edit
*That’s from memory so some of the names might be off. Like I said, Google will have all the answers.


#7

Hey , did you ever find a solution to this issue? I’m experiencing the same thing.