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

Vaprobash: /tmp/vagrant-shell: line 65: npm: command not found #585

Closed
zak10 opened this issue Oct 13, 2015 · 4 comments
Closed

Vaprobash: /tmp/vagrant-shell: line 65: npm: command not found #585

zak10 opened this issue Oct 13, 2015 · 4 comments
Labels
Milestone

Comments

@zak10
Copy link

zak10 commented Oct 13, 2015

As noted in #547, I am still experiencing the same error. I have the newest version of the repository and every time that I try to do a vagrant up (or vagrant provision on an already running box), I get this error.

Any thoughts on this one?

Just to clarify, line 285 of my Vagrantfile (which is what was changed in the commit that closed issue 547):
config.vm.provision "shell", path: "https://raw.githubusercontent.com/franzliedke/Vaprobash/patch-3/scripts/nodejs.sh", privileged: false, args: nodejs_packages.unshift(nodejs_version, github_url)

@franzliedke
Copy link
Contributor

Hmm, I can reproduce this, too. :-/

Too bad, I had thought I had fixed it. Will investigate, thanks for the heads-up.

@franzliedke
Copy link
Contributor

Found the culprit, I think. Testing my fix right now...

@franzliedke franzliedke added this to the 0.1.0-beta.3 milestone Oct 13, 2015
@franzliedke
Copy link
Contributor

Works now. Fixed this over here.

No need for you to update anything, just run vagrant destroy and vagrant up and you should be good to go. (Make sure config.php doesn't exist...)

@zak10
Copy link
Author

zak10 commented Oct 13, 2015

Works like a charm. Thanks!

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

No branches or pull requests

2 participants