Grunt error unable to find local grunt

If you’re seeing this message, either a Gruntfile wasn’t found or grunt hasn’t been installed locally to your project.

Solution 1:

 npm install -g grunt
  grunt:init  ( you will get following options ):
      jquery: A jQuery plugin
      node: A Node module
      commonjs: A CommonJS module
      gruntplugin: A Grunt plugin
      gruntfile: A Gruntfile (grunt.js)
  grunt init:jquery (if you want to create a jQuery related project.).

Solution for v1.4:

 npm install -g grunt-cli
 npm init
   fill all details and it will create a package.json file.
 npm install grunt (for grunt dependencies.)

Updated solution for new versions:

 npm install grunt --save-dev

Solution 2:

Install Grunt in node_modules rather than globally

npm install -g grunt

npm install grunt --save-dev

Solution 3:

npm install

Solution 4:

  "devDependencies": {
    "grunt": "~0.4.0",

Solution 5:

Grunt fatal error unable to find local grunt

This forum is closed. Thank you for your contributions.

Answered by:

Question

I use a custom deployment script when I deploy my node.js applciation to Azure WebApp.

Right after the npm install command, I want to execute a grunt command:

This fails during deployment, saying:

remote: Fatal error: Unable to find local grunt

That’s weird, because when I login into the kudu console and execute the exact same command, it succeeds.

• Edited by Peter Pan — MSFT Microsoft contingent staff Monday, April 4, 2016 1:39 AM add title header Node.js
• Edited by Gary Liu — MSFT Friday, July 1, 2016 6:20 AM edit title
• Moved by Gary Liu — MSFT Friday, July 1, 2016 6:20 AM move thread

Answers

I just tried this, just adding a grunt call to a default custom script. The problem is not that grunt is not found on the path. It definitely starts running, but it’s grunt itself that complains with:

And in fact if I got to Kudu console and run ‘grunt’ from the D:homesiterepository folder, it displays exactly the same thing.

So there is really nothing special about running it from a custom deployment script.

Источник

Fatal error: Unable to find local grunt. #584

I have uninstalled the old version,with npm uninstall -g grunt.and install the CLI,but I got this Error.

D:wwwgrunt-test>grunt -ddd
grunt-cli: The grunt command line interface. (v0.1.4)

Fatal error: Unable to find local grunt.

If you’re seeing this message, either a Gruntfile wasn’t found or grunt
hasn’t been installed locally to your project. For more information about
installing and configuring grunt, please see the Getting Started guide:

The text was updated successfully, but these errors were encountered:

@coolicer you need to install grunt locally to your project. See the section on «package.json» in the Getting Started guide, it explains what you need to do.

@tkellen it might be a good idea to mention earlier on in the guide how grunt needs to be installed locally, and what that actually means.

Made some updates with what I hope is even more obvious clarification.

@cowboy very thanks,Let me try again.
@tkellen thanks guy,try it.

I made it.I love you guys.

I got stuck on the same issue. Getting going with Grunt has been difficult, since all the tutorials I’ve found relate to 0.3.x releases:

My first impression is the official «getting started» guide is written for people familiar with NodeJS. I only installed Node to test out Grunt as a build process, so skipping over «extreme basics» is confusing. The guide jumps between installing, integrating with existing projects, and starting a new Grunt project — but it’s lacking an idiot-proof «Hello World» example. Hand-holding through each step with obvious explanations/tips/gotchas is a major help in the first few hours of learning.

I’ve hobbled to the point where calling grunt will run in my local project, but it fails because I don’t quite understand what the Gruntfile is doing.

I tried following other tutorials using templates to init a new project, but it’s not clear from the Grunt docs whether this needs to be installed separately and if a dependency needs to be added to package.json. Moreover how do npm commands fit into a Grunt workflow?

This is pure beginner’s ignorance, but the first three hours reading/trying hasn’t come easily. I think the «getting started» docs would benefit from a sequential nearly-useless example for acquaintance. Then link off to advanced topics / tutorials.

Источник

Fatal error: Unable to find local grunt. #761

I updated my generator-angular to 0.9.1 and I scaffold all my files. When I tried to use grunt it says: grunt-cli: The grunt command line interface. (v0.1.13)

Fatal error: Unable to find local grunt.

If you’re seeing this message, either a Gruntfile wasn’t found or grunt
hasn’t been installed locally to your project. For more information about
installing and configuring grunt, please see the Getting Started guide:

My yo version is 1.2.0, grunt version 0.4.5.

My file structure:

I do have gruntfile in my directory.

My choices for generator-angular

I noticed when I scaffolding, I got the following error:

pngquant-bin@0.3.1 postinstall /Users/stevemao/Documents/test-grunt-angular/node_modules/grunt-contrib-imagemin/node_modules/imagemin/node_modules/imagemin-pngquant/node_modules/pngquant-bin
node index.js

✗ pre-build test failed, compiling from source.
libpng-dev is installed

1 error generated.
make: *** [pngquant.o] Error 1
] killed: false, code: 2, signal: null >

The text was updated successfully, but these errors were encountered:

With the same enviro I don’t have any errors. What’s your node and npm version? Did you try to replicate the problem?

npm -v
1.4.9
node -v
v0.10.28

did you try running npm install ?

Hi guys, I can’t replicate the problem today. I would say it’s a caching issue. Is there any way to force clear cache just in case I see similar problem in the future?

npm cache clean is the way to go.

On Fri, Jun 27, 2014 at 10:08 AM, Mark Thomas notifications@github.com
wrote:

npm cache clean is the way to go.

—
Reply to this email directly or view it on GitHub
#761 (comment)
.

Kind Regards
Steve

Health Interact Pty Ltd
Level 12, 100 Miller St North Sydney NSW 2060

This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the system manager.
This message contains confidential information and is intended only for the
individual named. If you are not the named addressee you should not
disseminate, distribute or copy this e-mail. Please notify the sender
immediately by e-mail if you have received this e-mail by mistake and
delete this e-mail from your system. If you are not the intended recipient
you are notified that disclosing, copying, distributing or taking any
action in reliance on the contents of this information is strictly
prohibited.

Источник

scmGalaxy

A Platform for Software Engineers

Fatal error: Unable to find local grunt.

scmuser created the topic: Fatal error: Unable to find local grunt.
I am getting following error…

grunt lite
grunt-cli: The grunt command line interface. (v0.1.9)

Fatal error: Unable to find local grunt.

If you’re seeing this message, either a Gruntfile wasn’t found or grunt
hasn’t been installed locally to your project. For more information about
installing and configuring grunt, please see the Getting Started guide:

The command line tools are not included with the latest version of Grunt (0.4 at time of writing) instead you need to install them separately.

This is a good idea because it means you can have different versions of Grunt running on different projects but still use the nice concise grunt command to run them.

So first install the grunt cli tools globally:

npm install -g grunt-cli

(or possibly sudo npm install -g grunt-cli ).

You can establish that’s working by typing grunt –version

Now you can install the current version of Grunt local to your project. So from your project’s location…

npm install grunt –save-dev

The save-dev switch isn’t strictly necessary but is a good idea because it will mark grunt in its package.json devDependencies section as a development only module.

rajeshkumar replied the topic: Fatal error: Unable to find local grunt.
while running “npm install -g grunt-cli”, i got following code…

npm ERR! Error: No compatible version found: grunt-cli
npm ERR! No valid targets found.
npm ERR! Perhaps not compatible with your version of node?
npm ERR! at installTargetsError (/usr/share/npm/lib/cache.js:488:10)
npm ERR! at next_ (/usr/share/npm/lib/cache.js:438:17)
npm ERR! at next (/usr/share/npm/lib/cache.js:415:44)
npm ERR! at /usr/share/npm/lib/cache.js:408:5
npm ERR! at saved (/usr/share/npm/lib/utils/npm-registry-client/get.js:147:7)
npm ERR! at Object.oncomplete (/usr/lib/nodejs/graceful-fs.js:230:7)
npm ERR! You may report this log at:
npm ERR!
npm ERR! or use
npm ERR! reportbug –attach /home/scmbuild/npm-debug.log npm
npm ERR!
npm ERR! System Linux 3.2.0-53-generic
npm ERR! command “node” “/usr/bin/npm” “install” “-g” “grunt-cli”
npm ERR! cwd /home/scmbuild
npm ERR! node -v v0.6.12
npm ERR! npm -v 1.1.4
npm ERR! message No compatible version found: grunt-cli
npm ERR! message No valid targets found.
npm ERR! message Perhaps not compatible with your version of node?
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /home/scmbuild/npm-debug.log
npm not ok
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

rajeshkumar replied the topic: Fatal error: Unable to find local grunt.
Seems like node is older version so need to user latest…
How to upgrade nodes in Ubantu
Install the dependencies:

sudo apt-get install g++ curl libssl-dev apache2-utils
sudo apt-get install git-core

Run the following commands:

git clone git://github.com/ry/node.git
cd node
./configure
make
sudo make install

How to install grunt
Here’s what I did to fix this:

Uninstalled grunt globally:

npm uninstall -g grunt

Installed grunt-cli globally:

npm install -g grunt-cli

Then, in project root dir:

And all is good. Hope this works for anyone else running into this.
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

rajeshkumar replied the topic: Fatal error: Unable to find local grunt.
After running latest nodes, while using folliowing commands i got following error…”npm install -g grunt-cli”

rajeshkumar replied the topic: Fatal error: Unable to find local grunt.
From in stacekoverlfow..

Don’t download npm from aptitude or apt-get. Instead try:

git clone git://github.com/isaacs/npm.git
cd npm/scripts
chmod +x install.sh
sudo ./install.sh

saw it here: NPM can’t install appjs. Error: Cannot find module ‘graceful-fs’

Источник

fatal error: unable to find local grunt #290

Here’s the entire message on vagrant up:

At revision 27348.
Initializing grunt in WordPress develop. This may take a few moments.
grunt-cli: The grunt command line interface. (v0.1.13)

Fatal error: Unable to find local grunt.

If you’re seeing this message, either a Gruntfile wasn’t found or grunt
hasn’t been installed locally to your project. For more information about
installing and configuring grunt, please see the Getting Started guide:

So I’m headed for the Getting Started Guide. If anyone knows why grunt failed to load or install, please let me know.

The text was updated successfully, but these errors were encountered:

So I installed grunt-cli globally on my machine just in case but I still get the error. I can see the Gruntfile.js and the package.json file right there in the root of the wordpress-develop project where they belong. But still the error. I’m stumped. Any ideas?
os: Windows 8.1
ram: 12 G
Thanks for any help.
Dennis

I’m getting the same thing on both Windows 8.1 and a windows 7 machine.

I’m guessing this is due to the npm SSL issue. We probably need to verify how npm/node/grunt is installed inside the VM. http://blog.npmjs.org/post/78165272245/more-help-with-self-signed-cert-in-chain-and-npm

@dennis7742 The messaging in that error is «local» to the virtual machine, not to your computer. There is no need to install grunt locally. We should be able to get a fix for this in shortly.

Thanks for the report!

Ok, so this actually works on a fresh build of VVV. Likely because the new installation of npm comes without the self signed certs.

A couple things that could fix this.

1. vagrant destroy followed by vagrant up . This will retain all files and databases but destroy all server software and config. Having the machine go through provisioning again should cause the newest npm to install.
2. A series of commands to reinstall nodejs (and npm) by removing and then reprovisioning:
   • vagrant ssh
   • sudo apt-get purge nodejs (purge is required to remove config files)
   • exit
   • vagrant provision

Jeremy,
Thanks a lot for the reply. I’ll let you know how I come out. Sorry I missed you in Chicago last year. I’ve really been excited about using Vagrant & Puppet with WordPress dev since Tuts+ dealt with them a few months back. I also got a taste by installing them for Mathew Russel’s Mining the Social Web using IPy Notebooks hosted by Vagrant.

Sorry, but I went through both procedures and neither or both were able to yield a different result. I still get the same number build (or revision 27365) right before the error:

At revision 27365.
Initializing grunt in WordPress develop. This may take a few moments.
grunt-cli: The grunt command line interface. (v0.1.13)

Fatal error: Unable to find local grunt.

If you’re seeing this message, either a Gruntfile wasn’t found or grunt
hasn’t been installed locally to your project. For more information about
installing and configuring grunt, please see the Getting Started guide:

I got this exact same issue when npm was down about a month ago.

same here, windows 8.1

@dennis7742 Is it possible that the WordPress core Gruntfile.js is missing from www/wordpress-develop ?

@n1smo Are you getting this error with the most recent version of VVV?

had the error last wednesday, tried it several times on a new installation.

I gave it another try yesterday and for some reason the problem is fixed.

Just dropping by to say I see the same error.

Can confirm issue. Purged nodejs. Gruntfile is in the folder, grunt & grunt-cli v0.1.13 versions at latest stable. Windows 7.

I’m going to see if I can test this a bit locally to reproduce. Has anyone had success with running vagrant provision multiple times until it works? I’m wondering if the NPM server is not doing well at responding or if there’s something we can do to improve the connection on our end.

I wonder which version of Grunt runs: My local global install or the VM install? Both seem to be on the latest version, so there’s no chance to differentiate them.

Hi, I was asked by @franz-josef-kaiser to look into this. Without a real stacktrace there is no real debugging. I am puzzled why you would use a shell provisioner for such a large project. There is chef/puppet which let you organize your provisioning much nicer and also gives you stacktraces and debug output and logfiles about what happened, which makes it easier to pin down problems like this.

As a first step, maybe write all the stdout and stderr stuff into files so one can see what’s the real problem is?

@Sgoettschkes thanks for taking a look! It is difficult to track things down in VVV at times. Re proper provisioning, my thoughts in #258 (comment) explain that a bit.

I think this falls a bit in line with my reasoning for avoiding a proper provisioner. While it’s a fantastic technical answer for this type of thing for individual projects, the community benefits from having only the hurdles of Vagrant + shell to learn. At the same time, I use a provisioner in my day to day work because it’s amazing.

@franz-josef-kaiser Your local Grunt should never run due to VVV. The «local» that provisioning is referring to here is inside the VM. Likely it had trouble installing at some point during provisioning. I would think that a repeat vagrant provision would help here, but it’s tough to catch the errors.

Disregard my recent post. It was a permissions issue. Once I ran git bash as an administrator, I got much better results and although it still didn’t find the grunt file, it fixed it:

At revision 28220.
Initializing grunt in WordPress develop. This may take a few moments.

Local Npm module «grunt-contrib-qunit» not found. Is it installed?

Running «clean:all» (clean) task

Running «copy:files» (copy) task
Created 123 directories, copied 1080 files

Running «copy:wp-admin-rtl» (copy) task
Copied 1 files

Running «copy:version» (copy) task
Copied 1 files

Running «cssmin:core» (cssmin) task
File build/wp-admin/css/color-picker.min.css created.
File build/wp-admin/css/customize-controls.min.css created.
File build/wp-admin/css/customize-widgets.min.css created.
File build/wp-admin/css/deprecated-media.min.css created.
File build/wp-admin/css/ie.min.css created.
File build/wp-admin/css/install.min.css created.
File build/wp-admin/css/login.min.css created.
File build/wp-admin/css/wp-admin.min.css created.
File build/wp-includes/css/admin-bar.min.css created.
File build/wp-includes/css/buttons.min.css created.
File build/wp-includes/css/dashicons.min.css created.
File build/wp-includes/css/editor.min.css created.
File build/wp-includes/css/jquery-ui-dialog.min.css created.
File build/wp-includes/css/media-views.min.css created.
File build/wp-includes/css/wp-auth-check.min.css created.
File build/wp-includes/css/wp-pointer.min.css created.

Running «sass:colors» (sass) task
File build/wp-admin/css/colors/blue/colors.css created.
File build/wp-admin/css/colors/coffee/colors.css created.
File build/wp-admin/css/colors/ectoplasm/colors.css created.
File build/wp-admin/css/colors/light/colors.css created.
File build/wp-admin/css/colors/midnight/colors.css created.
File build/wp-admin/css/colors/ocean/colors.css created.
File build/wp-admin/css/colors/sunrise/colors.css created.

Running «autoprefixer:colors» (autoprefixer) task
File build/wp-admin/css/colors/blue/colors.css created.
File build/wp-admin/css/colors/coffee/colors.css created.
File build/wp-admin/css/colors/ectoplasm/colors.css created.
File build/wp-admin/css/colors/light/colors.css created.
File build/wp-admin/css/colors/midnight/colors.css created.
File build/wp-admin/css/colors/ocean/colors.css created.
File build/wp-admin/css/colors/sunrise/colors.css created.

Running «cssjanus:core» (cssjanus) task
File «build/wp-admin/css/about-rtl.css» created.
File «build/wp-admin/css/admin-menu-rtl.css» created.
File «build/wp-admin/css/color-picker-rtl.css» created.
File «build/wp-admin/css/common-rtl.css» created.
File «build/wp-admin/css/customize-controls-rtl.css» created.
File «build/wp-admin/css/customize-widgets-rtl.css» created.
File «build/wp-admin/css/dashboard-rtl.css» created.
File «build/wp-admin/css/deprecated-media-rtl.css» created.
File «build/wp-admin/css/edit-rtl.css» created.
File «build/wp-admin/css/farbtastic-rtl.css» created.
File «build/wp-admin/css/forms-rtl.css» created.
File «build/wp-admin/css/ie-rtl.css» created.
File «build/wp-admin/css/install-rtl.css» created.
File «build/wp-admin/css/l10n-rtl.css» created.
File «build/wp-admin/css/list-tables-rtl.css» created.
File «build/wp-admin/css/login-rtl.css» created.
File «build/wp-admin/css/media-rtl.css» created.
File «build/wp-admin/css/nav-menus-rtl.css» created.
File «build/wp-admin/css/press-this-rtl.css» created.
File «build/wp-admin/css/revisions-rtl.css» created.
File «build/wp-admin/css/themes-rtl.css» created.
File «build/wp-admin/css/widgets-rtl.css» created.
Nothing to flip in src/wp-admin/css/wp-admin.css
File «build/wp-includes/css/admin-bar-rtl.css» created.
File «build/wp-includes/css/buttons-rtl.css» created.
Nothing to flip in src/wp-includes/css/dashicons.css
File «build/wp-includes/css/editor-rtl.css» created.
File «build/wp-includes/css/jquery-ui-dialog-rtl.css» created.
File «build/wp-includes/css/media-views-rtl.css» created.
File «build/wp-includes/css/wp-auth-check-rtl.css» created.
File «build/wp-includes/css/wp-pointer-rtl.css» created.

Running «cssjanus:colors» (cssjanus) task
File «build/wp-admin/css/colors/blue/colors-rtl.css» created.
File «build/wp-admin/css/colors/coffee/colors-rtl.css» created.
File «build/wp-admin/css/colors/ectoplasm/colors-rtl.css» created.
File «build/wp-admin/css/colors/light/colors-rtl.css» created.
File «build/wp-admin/css/colors/midnight/colors-rtl.css» created.
File «build/wp-admin/css/colors/ocean/colors-rtl.css» created.
File «build/wp-admin/css/colors/sunrise/colors-rtl.css» created.

Running «cssmin:rtl» (cssmin) task
File build/wp-admin/css/color-picker-rtl.min.css created.
File build/wp-admin/css/customize-controls-rtl.min.css created.
File build/wp-admin/css/customize-widgets-rtl.min.css created.
File build/wp-admin/css/deprecated-media-rtl.min.css created.
File build/wp-admin/css/ie-rtl.min.css created.
File build/wp-admin/css/install-rtl.min.css created.
File build/wp-admin/css/login-rtl.min.css created.
File build/wp-admin/css/wp-admin-rtl.min.css created.
File build/wp-includes/css/admin-bar-rtl.min.css created.
File build/wp-includes/css/buttons-rtl.min.css created.
File build/wp-includes/css/editor-rtl.min.css created.
File build/wp-includes/css/jquery-ui-dialog-rtl.min.css created.
File build/wp-includes/css/media-views-rtl.min.css created.
File build/wp-includes/css/wp-auth-check-rtl.min.css created.
File build/wp-includes/css/wp-pointer-rtl.min.css created.

Running «cssmin:colors» (cssmin) task
File build/wp-admin/css/colors/blue/colors-rtl.min.css created.
File build/wp-admin/css/colors/blue/colors.min.css created.
File build/wp-admin/css/colors/coffee/colors-rtl.min.css created.
File build/wp-admin/css/colors/coffee/colors.min.css created.
File build/wp-admin/css/colors/ectoplasm/colors-rtl.min.css created.
File build/wp-admin/css/colors/ectoplasm/colors.min.css created.
File build/wp-admin/css/colors/light/colors-rtl.min.css created.
File build/wp-admin/css/colors/light/colors.min.css created.
File build/wp-admin/css/colors/midnight/colors-rtl.min.css created.
File build/wp-admin/css/colors/midnight/colors.min.css created.
File build/wp-admin/css/colors/ocean/colors-rtl.min.css created.
File build/wp-admin/css/colors/ocean/colors.min.css created.
File build/wp-admin/css/colors/sunrise/colors-rtl.min.css created.
File build/wp-admin/css/colors/sunrise/colors.min.css created.

Running «uglify:core» (uglify) task
File build/wp-admin/js/accordion.min.js created.
File build/wp-admin/js/color-picker.min.js created.
File build/wp-admin/js/comment.min.js created.
File build/wp-admin/js/common.min.js created.
File build/wp-admin/js/custom-background.min.js created.
File build/wp-admin/js/customize-controls.min.js created.
File build/wp-admin/js/customize-widgets.min.js created.
File build/wp-admin/js/dashboard.min.js created.
File build/wp-admin/js/edit-comments.min.js created.
File build/wp-admin/js/editor.min.js created.
File build/wp-admin/js/gallery.min.js created.
File build/wp-admin/js/image-edit.min.js created.
File build/wp-admin/js/inline-edit-post.min.js created.
File build/wp-admin/js/inline-edit-tax.min.js created.
File build/wp-admin/js/link.min.js created.
File build/wp-admin/js/media-gallery.min.js created.
File build/wp-admin/js/media-upload.min.js created.
File build/wp-admin/js/media.min.js created.
File build/wp-admin/js/nav-menu.min.js created.
File build/wp-admin/js/password-strength-meter.min.js created.
File build/wp-admin/js/plugin-install.min.js created.
File build/wp-admin/js/post.min.js created.
File build/wp-admin/js/postbox.min.js created.
File build/wp-admin/js/revisions.min.js created.
File build/wp-admin/js/set-post-thumbnail.min.js created.
File build/wp-admin/js/svg-painter.min.js created.
File build/wp-admin/js/tags.min.js created.
File build/wp-admin/js/theme.min.js created.
File build/wp-admin/js/updates.min.js created.
File build/wp-admin/js/user-profile.min.js created.
File build/wp-admin/js/user-suggest.min.js created.
File build/wp-admin/js/widgets.min.js created.
File build/wp-admin/js/word-count.min.js created.
File build/wp-admin/js/wp-fullscreen.min.js created.
File build/wp-admin/js/xfn.min.js created.
File build/wp-includes/js/admin-bar.min.js created.
File build/wp-includes/js/autosave.min.js created.
File build/wp-includes/js/backbone.min.js created.
File build/wp-includes/js/colorpicker.min.js created.
File build/wp-includes/js/comment-reply.min.js created.
File build/wp-includes/js/customize-base.min.js created.
File build/wp-includes/js/customize-loader.min.js created.
File build/wp-includes/js/customize-models.min.js created.
File build/wp-includes/js/customize-preview-widgets.min.js created.
File build/wp-includes/js/customize-preview.min.js created.
File build/wp-includes/js/customize-views.min.js created.
File build/wp-includes/js/heartbeat.min.js created.
File build/wp-includes/js/hoverIntent.min.js created.
File build/wp-includes/js/json2.min.js created.
File build/wp-includes/js/masonry.min.js created.
File build/wp-includes/js/mce-view.min.js created.
File build/wp-includes/js/media-audiovideo.min.js created.
File build/wp-includes/js/media-editor.min.js created.
File build/wp-includes/js/media-models.min.js created.
File build/wp-includes/js/media-views.min.js created.
File build/wp-includes/js/quicktags.min.js created.
File build/wp-includes/js/shortcode.min.js created.
File build/wp-includes/js/tw-sack.min.js created.
File build/wp-includes/js/underscore.min.js created.
File build/wp-includes/js/utils.min.js created.
File build/wp-includes/js/wp-ajax-response.min.js created.
File build/wp-includes/js/wp-auth-check.min.js created.
File build/wp-includes/js/wp-backbone.min.js created.
File build/wp-includes/js/wp-list-revisions.min.js created.
File build/wp-includes/js/wp-lists.min.js created.
File build/wp-includes/js/wp-pointer.min.js created.
File build/wp-includes/js/wp-util.min.js created.
File build/wp-includes/js/wpdialog.min.js created.
File build/wp-includes/js/wplink.min.js created.
File build/wp-includes/js/zxcvbn-async.min.js created.
File build/wp-includes/js/plupload/handlers.min.js created.
File build/wp-includes/js/plupload/wp-plupload.min.js created.
File build/wp-includes/js/tinymce/plugins/wordpress/plugin.min.js created.
File build/wp-includes/js/tinymce/plugins/wpdialogs/plugin.min.js created.
File build/wp-includes/js/tinymce/plugins/wpeditimage/plugin.min.js created.
File build/wp-includes/js/tinymce/plugins/wpfullscreen/plugin.min.js created.
File build/wp-includes/js/tinymce/plugins/wpgallery/plugin.min.js created.
File build/wp-includes/js/tinymce/plugins/wplink/plugin.min.js created.
File build/wp-includes/js/tinymce/plugins/wpview/plugin.min.js created.

Running «concat:tinymce» (concat) task
File «build/wp-includes/js/tinymce/wp-tinymce.js» created.

Running «compress:tinymce» (compress) task
Created build/wp-includes/js/tinymce/wp-tinymce.js.gz (122989 bytes)

Running «clean:tinymce» (clean) task
Cleaning build/wp-includes/js/tinymce/wp-tinymce.js. OK

Running «jsvalidate:build» (jsvalidate) task
256 files are valid.

Done, without errors.
PHPMyAdmin already installed.

Restarting nginx nginx
. done.
Cleaning the virtual machine’s /etc/hosts file.
Adding domains to the virtual machine’s /etc/hosts file.
from /srv/www/vvv-hosts
from /srv/www/vvv-hosts.dev
from /srv/www/vvv-hosts-trunk.dev
from /srv/www/vvv-hostsevelop.dev
from /srv/www/vvv-hosts-develop.dev

VAGRANT: 021f986a87aa6a5a6c50f90e04d3c0c9 (default) / bf2a65bc-7b17-4431-b368

Источник