I've installed all the prerequisites- sass, compass, Bower,Bundler, Yeoman,...
on running the command yo aurora I get:
Error: Cannot find module './build/Release/shell'
at Function.Module._resolveFilename (module.js:338:15)
at Function.Module._load (module.js:280:25)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at Object. (/usr/local/lib/node_modules/generator-aurora/node_modules/execSync/index.js:30:11)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:364:17)
so I can't create a subtheme.
What should I do?
Comments
Comment #1
ricksta CreditAttribution: ricksta commentedI've since fixed this by writing "compass create gd -r aurora --using aurora" in the terminal. This was not in the official documention for Aurora, but I found it elsewhere and it worked so problem solved.
Comment #2
iamcarrico CreditAttribution: iamcarrico commentedWhat system are you on? And what version of the generator are you using?
Note: The compass-generated theme is not supported anymore, and could have unexpected results if you want to use Sass 3.3+.
Comment #3
promount CreditAttribution: promount commentedHi, I'm getting the exact same error on Mac 10.10. Not sure what the generator's version is but when I installed it I got
generator-aurora@0.3.0 /usr/local/lib/node_modules/generator-aurora...
Any help would be highly appreciated.
Comment #4
iamcarrico CreditAttribution: iamcarrico commentedThis is a problem with ExecSync— https://github.com/mgutz/execSync/issues/27
Comment #5
promount CreditAttribution: promount commentedGreat. Thanks iamcarrico. However I don't understand the solution/workaround they give in the link you provided. Since I don't get what node-gyp is and how should I use it and as far as can say I already use python 2.7, I'd like to ask you if there's a quick way to start using aurora or just wait for ExecSync to be fixed. Thanks again for your time.
Comment #6
esod CreditAttribution: esod commentedI got the same error. I am seeing this issue with other stacks too. (See at https://github.com/gordonwritescode/gitty/issues/43).
I've gotten past it by installing node v0.10.36 instead. I'm using homebrew, so this isn't too big a deal:
Comment #7
codev0 CreditAttribution: codev0 commentedThanks esod, very helpful.
But I faced with a problem with brew permissions. Brew can't add link to node.
I solved this with
sudo chown -R whoami /usr/local
Comment #8
davidfells81@gmail.com CreditAttribution: davidfells81@gmail.com commentedStill experiencing this... any progress? An actual fix aside from changing the node version (which isn't easy if you didn't install with homebrew, nvm has it's own suite of issues)
Comment #9
rho_ CreditAttribution: rho_ as a volunteer commentedThis still seems to be occurring. @iamcarrico is correct about execSync, but that module will remain a problem for folks running python 3 or node 0.12. As suggested in the execSync issue, exec-sync should be used as a replacement. It solves a lot of the python/node version issues.
Comment #10
rho_ CreditAttribution: rho_ as a volunteer commentedDigging a bit deeper, it looks like this very thing was addressed in the generator-drupal-theme issues. It appears the fix is there, but has not been rolled into a tag therefore will not come down with an
npm install
.Comment #11
iamcarrico CreditAttribution: iamcarrico as a volunteer commentedWhoops. I pushed a release. Sorry all y'all—