Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rx.js error prevents me from scafolfding #32

Open
krampstudio opened this issue May 9, 2016 · 2 comments
Open

rx.js error prevents me from scafolfding #32

krampstudio opened this issue May 9, 2016 · 2 comments

Comments

@krampstudio
Copy link

I'm unable to run the generator, rx.js throws without any details:

/home/bertrand/.nvm/versions/node/v6.1.0/lib/node_modules/yo/node_modules/rx/dist/rx.js:77
    throw e;

The error appear from a fresh install, I've tried with different versions of node and yo.

nvm install v6.1.0
npm install -g yo generator-gruntplugin
mkdir grunt-food && cd grunt-food
yo gruntplugin
(node:9751) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
undefined
For more information about Grunt plugin best practices,
please see the docs at http://gruntjs.com/creating-plugins
? Plugin Name grunt-food


/home/bertrand/.nvm/versions/node/v6.1.0/lib/node_modules/yo/node_modules/rx/dist/rx.js:77
    throw e;
    ^
grunt-food
➜  grunt-foodfact yo --version && echo $PATH $NODE_PATH && node -e 'console.log(process.platform, process.versions)'
1.8.1
/home/bertrand/.nvm/versions/node/v6.1.0/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
linux { http_parser: '2.7.0',
  node: '6.1.0',
  v8: '5.0.71.35',
  uv: '1.9.0',
  zlib: '1.2.8',
  ares: '1.10.1-DEV',
  icu: '56.1',
  modules: '48',
  openssl: '1.0.2h' }
@krampstudio
Copy link
Author

I've tried to capture the stack, but it seems errors are thrown in cascade, see https://gist.github.com/krampstudio/b6b1dd7d3475bee120d11e47c04cbabd

@kevindashgit
Copy link

running into the same issue - maybe it has something to do with node and/or npm version? (which for me are 0.12.13 and 2.15.0 respectively).

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

No branches or pull requests

2 participants