jasondavies / science.js

Scientific and statistical computing in JavaScript.
http://www.jasondavies.com/
Other
886 stars 93 forks source link

errors installing with npm 1.1.13 or newer #6

Closed stepheneb closed 12 years ago

stepheneb commented 12 years ago

I'm getting errors using npm versions 1.1.13 or later installing science.js.

The error starts occurring after this commit in npm: https://github.com/isaacs/npm/commit/ed2a3c1090aa4c7

[science.js-git (master)]$ npm -v
1.1.18

[science.js-git (master)]$ npm install . -g
npm ERR! error reading .
npm ERR! couldn't pack . to /var/folders/zK/zK+A4xtxHSevr7D+EoIsPE+++TQ/-Tmp-/npm-1334863687383/1334863687383-0.24840772151947021/tmp.tgz
npm ERR! Could not install: .

npm ERR! SyntaxError: Unexpected token }
npm ERR!     at Object.parse (native)
npm ERR!     at Packer.readRules (/usr/local/lib/node_modules/npm/node_modules/fstream-npm/fstream-npm.js:179:33)
npm ERR!     at Packer.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/fstream-npm/node_modules/fstream-ignore/ignore.js:132:22)
npm ERR!     at [object Object].<anonymous> (fs.js:123:5)
npm ERR!     at [object Object].emit (events.js:64:17)
npm ERR!     at fs.js:1181:12
npm ERR!     at Object.oncomplete (/usr/local/lib/node_modules/npm/node_modules/graceful-fs/graceful-fs.js:94:5)
npm ERR! You may report this log at:
npm ERR!     <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR!     <npm-@googlegroups.com>
npm ERR! 
npm ERR! System Darwin 10.8.0
npm ERR! command "node" "/usr/local/bin/npm" "install" "." "-g"
npm ERR! cwd /Users/stephen/dev/javascript/d3/science.js-git
npm ERR! node -v v0.6.15
npm ERR! npm -v 1.1.18
npm ERR! file /Users/stephen/dev/javascript/d3/science.js-git/lib/uglifyjs/package.json
npm ERR! path /Users/stephen/dev/javascript/d3/science.js-git/lib/uglifyjs
npm ERR! type unexpected_token
npm ERR! fstream_path /Users/stephen/dev/javascript/d3/science.js-git/lib/uglifyjs
npm ERR! fstream_type Directory
npm ERR! fstream_class Packer
npm ERR! arguments [ '}' ]
npm ERR! message Unexpected token }
npm ERR! fstream_stack Packer.readRules (/usr/local/lib/node_modules/npm/node_modules/fstream-npm/fstream-npm.js:182:10)
npm ERR! fstream_stack Packer.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/fstream-npm/node_modules/fstream-ignore/ignore.js:132:22)
npm ERR! fstream_stack [object Object].<anonymous> (fs.js:123:5)
npm ERR! fstream_stack [object Object].emit (events.js:64:17)
npm ERR! fstream_stack fs.js:1181:12
npm ERR! fstream_stack Object.oncomplete (/usr/local/lib/node_modules/npm/node_modules/graceful-fs/graceful-fs.js:94:5)

npm ERR! TypeError: Cannot call method 'filter' of undefined
npm ERR!     at Packer.addIgnoreRules (/usr/local/lib/node_modules/npm/node_modules/fstream-npm/node_modules/fstream-ignore/ignore.js:148:13)
npm ERR!     at Packer.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/fstream-npm/node_modules/fstream-ignore/ignore.js:133:10)
npm ERR!     at [object Object].<anonymous> (fs.js:123:5)
npm ERR!     at [object Object].emit (events.js:64:17)
npm ERR!     at fs.js:1181:12
npm ERR!     at Object.oncomplete (/usr/local/lib/node_modules/npm/node_modules/graceful-fs/graceful-fs.js:94:5)
npm ERR! You may report this log at:
npm ERR!     <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR!     <npm-@googlegroups.com>
npm ERR! 
npm ERR! System Darwin 10.8.0
npm ERR! command "node" "/usr/local/bin/npm" "install" "." "-g"
npm ERR! cwd /Users/stephen/dev/javascript/d3/science.js-git
npm ERR! node -v v0.6.15
npm ERR! npm -v 1.1.18
npm ERR! type non_object_property_call
npm ERR! arguments [ 'filter', undefined ]
npm ERR! message Cannot call method 'filter' of undefined
npm ERR! 
npm ERR! Additional logging details can be found in:
npm ERR!     /Users/stephen/dev/javascript/d3/science.js-git/npm-debug.log
npm not ok
stepheneb commented 12 years ago

FYI: I am installing science.js from a local checkout of the repository -- not from an online npm package since science.js isn't in the npm repository.

stepheneb commented 12 years ago

Could be an npm issue ... created npm issue here with link back: https://github.com/isaacs/npm/issues/2385