grunt packaged not installed for wordpress-develop on first vagrant up

[ericandrewlewis]

The grunt package should be installed, as it's specified in wordpress-develop's package.json.

However, it is not installed on first vagrant up, although other packages are installed.

To investigate, I made logs of npm install appear rather than be swallowed to dev/null, and see this output.

If I login to the machine after provisioning and run npm install, it installs grunt as well as grunt-jsvalidate.

vagrant@vvv:/srv/www/wordpress-develop$ npm install
[email protected] /srv/www/wordpress-develop
├─┬ [email protected] 
│ └── [email protected] 
└─┬ [email protected] 
  └── [email protected] 

[jeremyfelt]

Good catch, I haven't tried using grunt inside the VM in a while.

It seems like the related issue could be this line: UNMET PEER DEPENDENCY grunt@~0.4.0.

I wonder if this is somehow related to #788 and #779.

[jeremyfelt]

I think we need to test this a bit more. I ran through vagrant up from scratch last week and grunt installed fine as part of provisioning.

[jeremyfelt]

I did another vagrant up with a blank box today as part of 1.3.0 testing and things seemed ok. I'm wondering if this was a one off issue.

[ntwb]

GruntJS 1.0.0 was released today http://gruntjs.com/blog/2016-04-04-grunt-1.0.0-released

Grunt-cli is also now 1.x, currently 1.2.0 https://github.com/gruntjs/grunt-cli

On a fresh VVV setup and an initial vagrant up and subsequent vagrant up --provision I've currently got:

vagrant@vvv:/srv/www/wordpress-develop$ grunt --version
grunt-cli v1.2.0
grunt v0.4.5

This all appears correct as Grunt 0.4.5 is what we currently install for WordPress (src)

[GaryJones]

I'm not sure if this is related, but I recently uninstalled global Grunt on my host machine (preferring all projects to include their own dependencies), and I'm now getting the following:

After updating everything (VVV develop branch, latest box version, halted then vagrant up --provision), I then still got the same warning, but provisioning seemed to carry on:

There was an entry to say that Grunt was being installed, but even at the end, the error persisted:

[jeremyfelt]

I was able to reproduce this today on a fresh vagrant up with the develop branch. The resulting npm-debug.log has a couple errors at the end that may be relevant.

It then took too many destroys and re-provisions, but I think I found how to reproduce.

In provision.sh, we have noroot npm install &>/dev/null for wordpress-develop on the first provision.

If I allow npm output to be shown by changing that to noroot npm install for a fresh provision, it works fine. If I change it back to noroot npm install &>/dev/null for a fresh position, it has the same error.

Now that I'm there, I haven't dug into possible reasons yet, but a short term fix may just be to allow for the output.

[jeremyfelt]

This appears to be related, if not the issue: npm/npm#9633

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.