npm install does not catch jsonparse module

[max-mapper]

npm install does not catch jsonparse module

[max-mapper]

in the log output above the first time you ran npm install it only installed csv and couchapp. the most recent version of package.json has more modules than that: https://github.com/maxogden/datacouch/blob/node_server/package.json

are you sure it was a complete fresh clone of the HEAD of the node_server branch?

[shuhblam]

that is a good point. i thought that is what i was doing when i ran

git checkout -b node_server_dev upstream/node_server

but i think it only did csv because npm was smart enough to see that I already had some of the other modules installed before hand. let me run npm install from a brand new clone and see what happens.

[shuhblam]

brand new clone install output

Coles-MacBook-Air:datacouch cole$ npm install
npm WARN [email protected] dependencies field should be hash of : pairs
npm http GET https://registry.npmjs.org/couchapp/0.8.1
npm http GET https://registry.npmjs.org/csv/0.0.10
npm http 304 https://registry.npmjs.org/csv/0.0.10
npm http 304 https://registry.npmjs.org/couchapp/0.8.1
[email protected] ./node_modules/couchapp
[email protected] ./node_modules/csv
Coles-MacBook-Air:datacouch cole$ node run
The "sys" module is now called "util". It should have a similar interface.

node.js:201
throw e; // process.nextTick error, or 'error' event on first tick
^
Error: Cannot find module 'jsonparse'
at Function._resolveFilename (module.js:334:11)
at Function._load (module.js:279:25)
at Module.require (module.js:357:17)
at require (module.js:368:17)
at Object. (/Users/cole/Public/datacouch/node_modules/JSONStream/index.js:2:14)
at Module._compile (module.js:432:26)
at Object..js (module.js:450:10)
at Module.load (module.js:351:31)
at Function._load (module.js:310:12)
at Module.require (module.js:357:17)

[shuhblam]

that does not seem right...

[dominictarr]

can you paste in npm ls after the install?

hmm, it appears that this my be related to JSONStream, which seems odd. does it work if you install JSONStream directly?

[max-mapper]

@dominictarr the issue was that you checked in your .gitignore with JSONStream and then when I checked in JSONStream it didn't include the node_modules inside, so when @colegillespie did npm install his npm saw that he already had JSONStream in node_modules and skipped installation, but npm didn't realize that JSONStream was missing a dependency.

[dominictarr]

okay, but I want the .gitignore in my repo because I don't want node_modules in my reusable lib's repo.

but you want it in your deployable app here, so feels like a catch 22.
I could use a global .gitignore, but that would mess up my apps.

so what is the solution here?

an .npmignore that ignores .gitignore?

[shuhblam]

You could always just add your node_modules later once you delete the node_modules dir and your .gitignore and leave them untracked by git ya know. Just do not "git add" them.

[dominictarr]

oh, all I need to do is republish JSONStream

https://github.com/isaacs/npm/issues/1862

npm now automatically uses .gitignore as npm ignore.

[dominictarr]

okay, just published JSONStream 1.1.3

try that.

[max-mapper]

jsonstream 0.1.3 successfully installs jsonparse