Skip to content
This repository has been archived by the owner on May 28, 2019. It is now read-only.

"Hacking on Ace" installation step failed #10

Open
greenwich opened this issue May 6, 2012 · 5 comments
Open

"Hacking on Ace" installation step failed #10

greenwich opened this issue May 6, 2012 · 5 comments

Comments

@greenwich
Copy link

What should be done with "Hacking on Ace" step? Because it gives following error:

./Makefile.dryice.js normal gives following:

using targetDir ' build '
ace ---------

node.js:201
throw e; // process.nextTick error, or 'error' event on first tick
^
TypeError: Cannot call method 'map' of undefined
at new CommonJsProject (/usr/lib/node_modules/dryice/lib/dryice/index.js:666:27)
at Function.createCommonJsProject (/usr/lib/node_modules/dryice/lib/dryice/index.js:974:10)
at Object. (gherkin-editor/vendor/ace/Makefile.dryice.js:104:20)
at Module._compile (module.js:441:26)
at Object..js (module.js:459:10)
at Module.load (module.js:348:31)
at Function._load (module.js:308:12)
at Array.0 (module.js:479:10)
at EventEmitter._tickCallback (node.js:192:40)

@patcon
Copy link

patcon commented Apr 16, 2013

For what it's worth, I got this working using nvm to install node v0.4.12. I did have to update the jasmin-node package from 1.0.4 to 1.0.6 in packages.json.

Cheers!

@jdar
Copy link

jdar commented May 10, 2013

patcon ... any other hints? :) I upgraded and re-installed, but still getting the error. maybe you changed something else too?

@patcon
Copy link

patcon commented May 10, 2013

upgraded? it's a big downgrade to get to node v0.4.12, just to make sure we're on the same page :)

But sorry, other than that, I think I explained everything I did to skirt around the error.

@jdar
Copy link

jdar commented May 10, 2013

thanks for the reply.

If I can trouble you for one more tidbit: what version of npm are you
running?

I had intended to upgrade this project to v0.10, but now i'll be happy just
to get autocomplete working.

D

@patcon
Copy link

patcon commented May 10, 2013

No sweat! Seem even when using v0.4.12 of node via nvm, npm --version still gives 1.2.0, which is the same as my system version of npm. Kinda surprised me that this is the case, but apparently that's how nvm works

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants