ignite: Cannot read property 'forEach' of undefined #3

Closed
nickiv opened this Issue Oct 3, 2012 · 1 comment

Projects

None yet

3 participants

@nickiv
nickiv commented Oct 3, 2012

Hello!

I'm trying to run ignite.js examples under node 0.8.11, but even when I run ignite executable without parameters exception is thrown:

[root@fedora15 ignite]# ./bin/ignite examples/hello_world.js

/root/ignite/node_modules/underscore/underscore.js:77
if (nativeForEach && obj.forEach === nativeForEach) {
^
TypeError: Cannot read property 'forEach' of undefined
at Function..each..forEach (/root/ignite/node_modules/underscore/underscore.js:77:29)
at /root/ignite/bin/ignite:169:9
at .reduce..foldl..inject (/root/ignite/node_modules/underscore/underscore.js:116:25)
at .each..forEach (/root/ignite/node_modules/underscore/underscore.js:86:24)
at Function.
.reduce..foldl..inject (/root/ignite/node_modules/underscore/underscore.js:111:5)
at parseChunk (/root/ignite/bin/ignite:162:20)
at cmdLineHandling (/root/ignite/bin/ignite:228:12)
at Object. (/root/ignite/bin/ignite:309:11)
at Module._compile (module.js:449:26)
at Object.Module._extensions..js (module.js:467:10)

Also tried 0.6.21, still same exception.

Do anybody have any suggestions?

@richardms
Collaborator

Hi,

Sorry it's taken a couple of days to reply - they've been rather hectic, but I've finally had a chance to investigate this.

It's a version problem - specifically of underscore, which recently went from 1.3.x to 1.4.x and seems a little more strict. It seems that there are a few places that trigger the error that you saw, so we'll need to go through and find these. In the meantime, I have changed the package.json file such that it installs the latest 1.3.x version of underscore, which fixes the problem.

If you used npm to get ignite then just delete what you have and get it again. If you have a git clone, do:

git pull
rm -rf node_modules
npm install

Any more problems, please let us know!

Richard

@ignitejs ignitejs closed this Jun 8, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment