Grunt init task fails on shell:ember:dev

Hi,

I’ve been installing Vagrant box and because of problems I’ve been researching why Grunt-Vagrant fails: https://github.com/TryGhost/Ghost-Vagrant/issues/60 https://github.com/TryGhost/Ghost-Vagrant/issues So I’ve made a clean clone of Ghost and just followed instructions from README.md and it appears that described procedure fails when running:

grunt init

...
Running "shell:ember:dev" (shell) task
/bin/sh: /Users/piotrblazejewicz/git/Ghost/core/client/node_modules/.bin/ember: No such file or directory
Warning: Command failed: /bin/sh: /Users/piotrblazejewicz/git/Ghost/core/client/node_modules/.bin/ember: No such file or directory
 Use --force to continue.

Aborted due to warnings.

https://github.com/TryGhost/Ghost/blob/master/Gruntfile.js#L284-L285

The init task is used in other task, so for example grunt validate described in Ghost-Vagrant docs also fails.

I’m using up-to-date master with latest commit 6db9826b237e36f72efc03215ac6f2e29cc7769d and with clean node_modules directory.

Can someone confirm this?

[ErisDS]

npm install doesn’t always complete properly. Any one of a number of things can go wrong, so when getting errors like this the first thing to do is just try again. Running npm cache clear beforehand will delete your local cache of modules to install, just incase something went wrong there.

If that doesn’t help you, try deleting the node_modules folders. There’s one at /node_modules and one at /core/client/node_modules. Alternatively you can do:

rm -rf core/client git checkout -- core/client

To delete the client folder, and grab it from git again. This deletes all of the files that have been fetched or built and gives you a clean slate to start from.

[JonathanRosado]

Thanks @ErisDS