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

rackt init <name> failed: node_modules/.bin/originate: No such file or directory #22

Closed
benlesh opened this issue Jan 18, 2016 · 2 comments

Comments

@benlesh
Copy link

benlesh commented Jan 18, 2016

Here's what I got the first time I tried to use rackt-cli:

rackt init rackt-test

/usr/local/Cellar/nvm/0.25.4/versions/node/v5.0.0/lib/node_modules/rackt-cli/bin/../tasks/init: line 5: /usr/local/Cellar/nvm/0.25.4/versions/node/v5.0.0/lib/node_modules/rackt-cli/bin/..//node_modules/.bin/originate: No such file or directory

I've tried uninstalling rackt-cli and reinstalling it, but no dice.

Node version 5.0.0
npm version 3.3.10

@mzabriskie
Copy link
Owner

It's a problem with rackt-cli not being compatible with npm 3. I need to fix this, but haven't had time.

@benlesh
Copy link
Author

benlesh commented Jan 18, 2016

Makes sense. I'd have dug into it, but I don't have the time either. LOL. I suspect you're going to get a lot of that with a CLI tool. People who need time-savers don't often have time to contribute.

mzabriskie added a commit that referenced this issue Jul 8, 2016
Put local node_modules/.bin in PATH, fixes #22
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