npm install fails #4

jscheel opened this Issue Mar 10, 2011 · 4 comments


None yet
4 participants

jscheel commented Mar 10, 2011


npm info it worked if it ends with ok
npm info using npm@0.3.7
npm info using node@v0.4.1
npm info fetch
npm ERR! couldn't read package.json in /tmp/npm-1299775291602/1299775291602-0.8720391236711293/contents/package
npm ERR! Error installing soupselect@0.2.0
npm ERR! Error: Failed to parse json
npm ERR! Unexpected token ]
npm ERR! at jsonParseFail (/usr/local/lib/node/.npm/npm/0.3.7/package/lib/utils/read-json.js:89:11)
npm ERR! at /usr/local/lib/node/.npm/npm/0.3.7/package/lib/utils/read-json.js:82:14
npm ERR! at P (/usr/local/lib/node/.npm/npm/0.3.7/package/lib/utils/read-json.js:62:40)
npm ERR! at cb (/usr/local/lib/node/.npm/npm/0.3.7/package/lib/utils/graceful-fs.js:31:9)
npm ERR! at [object Object]. (fs.js:86:5)
npm ERR! at [object Object].emit (events.js:39:17)
npm ERR! at afterRead (fs.js:843:12)
npm ERR! JSON.parse
npm ERR! JSON.parse Failed to parse package.json data.
npm ERR! JSON.parse Note that package.json must be actual JSON, not
npm ERR! JSON.parse just a JavaScript object.
npm ERR! JSON.parse
npm ERR! JSON.parse This changed in npm 0.3.0, and is not a bug in npm.
npm ERR! JSON.parse Tell the package author to fix their package.json file.
npm ERR! JSON.parse
npm ERR! System Darwin 10.6.0
npm not ok

If the commit was made, it still hasn't appeared in npm. For now you can download the .tgz from npm repository, extract and edit package.json to remove the trailing comma from the git line and use the npm install {folder} option.

jscheel commented Apr 5, 2011


rjack commented Apr 24, 2011

npm package is still broken. Could you please publish the fix?

We just published your code (unmodified, with author untouched) as da-soupselect ... so we can actually use it in production. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment