BodyParser 1.0.1 - ENOENT on install about allcountjs HOT 5 CLOSED

I should add that I also saw this error on Q as well. Never saw an issue with underscore though. Those appear to be the only static versioned dependencies in the package.json file.

Edit: I should read closer before I post, there are of course more than just these 3 but only Q and body-parser have thrown the error.

Further Edit: Rather than string a list of comments I'm adding this here. The issue appears to have to do with body-parser 1.0.1 having a qs@~0.6.6 dependency (https://github.com/hapijs/qs). The oldest available version of qs is 1.0. First version of body-parser that moves qs to > 1.0.0 is 1.6.0.

from allcountjs.

I'm closing this. I reinstalled nodejs (and symlinked to node) on my Debian server and now it's working. Same uninstall/reinstall worked on Windows as well. I have no idea what happened to cause it, but I'm not the only one on these servers working with node so it may have just been broken at some point.

from allcountjs.

Hello Jeremy!
Nice to hear that you've resolved it. Have you installed allcountjs as global or as local dependency? Seems to be a failed install issue. Maybe npm update could help in such situation.
Thanks for describing your case!

from allcountjs.

Oddly npm update didn't help me and I realized I the install had an issue when sudo npm came back saying it couldn't find the file (non elevated npm was fine) . The problem ended up being an attempted NVM node install, turns out they were having bower issues and didn't just do the symlink. In doing so both nodejs and npm packages were broken. That explains the Linux server issues but I still have no idea why I got the same error on Windows.... I'm going to chalk it up to losing track of vm windows and mistaking bash for git bash in Windows. I can't get it to repro for me anyway so I'd rather just plead PEBKAC.

from allcountjs.

Yeah. It's weird. Anyway thanks for filing it! Could be helpful for people who experienced same issue.

from allcountjs.