grunt-cli

npm WARN deprecated lodash@2.4.2: lodash@<3.0.0 is no longer maintained

由 点点圈 提交于 2019-12-03 23:23:37
问题 I'm getting an error when using npm to install grunt-cli globally. It's related to lodash: npm WARN deprecated lodash@2.4.2: lodash@<3.0.0 is no longer maintained. Upgrade to lodash@^3.0.0. Here are the versions i'm using, and the list of global packages installed. node: v5.1.0 npm: v3.5.0 npm list -g: http://pastebin.com/NuJU3bY0 I've attempted to install the latest version of lodash (v3.10.1) globally, but I still got the error again after uninstalling my grunt-cli global package, and then

npm WARN deprecated lodash@2.4.2: lodash@<3.0.0 is no longer maintained

由 孤街醉人 提交于 2019-12-01 02:16:55
I'm getting an error when using npm to install grunt-cli globally. It's related to lodash: npm WARN deprecated lodash@2.4.2: lodash@<3.0.0 is no longer maintained. Upgrade to lodash@^3.0.0. Here are the versions i'm using, and the list of global packages installed. node: v5.1.0 npm: v3.5.0 npm list -g: http://pastebin.com/NuJU3bY0 I've attempted to install the latest version of lodash (v3.10.1) globally, but I still got the error again after uninstalling my grunt-cli global package, and then re-installing my global package. Below is the installation log: sudo npm install lodash -g /usr/local

TFS Build cannot find Grunt

由 时光毁灭记忆、已成空白 提交于 2019-11-30 05:32:45
问题 I have installed npm and grunt on our TFS build server. I installed the grunt-cli using npm install -g grunt-cli and was then able to run grunt deploy from the command line when logged in as myself. Out TFS builds run as the tfsservice user though, and when it attempts to do grunt deploy it gets an error message that: 'grunt' is not recognized as an internal or external command, operable program or batch file. So, while logged in as myself on the build server, if I run the command prompt as

Jenkins integration with Grunt

由 二次信任 提交于 2019-11-28 09:03:19
I've setup Jenkins v1.550 on Windows Server 2008 R2. It runs as a service at http://localhost:8080 for now. I'm logged into the machine as an Administrator. I've installed Node.js and can run "npm" from the command line. I've also installed the NodeJS plugin v0.2.1 for Jenkins. I then went into the Configure System section of Jenkins, scrolled down to NodeJS installations, clicked on Add NodeJS button, gave "NodeJS" as the name, and "C:\Program Files\nodejs" as the path to the installation directory. I didn't check the "Install automatically" option as I read on the plugin page that it is only

Jenkins integration with Grunt

由 和自甴很熟 提交于 2019-11-27 02:36:38
问题 I've setup Jenkins v1.550 on Windows Server 2008 R2. It runs as a service at http://localhost:8080 for now. I'm logged into the machine as an Administrator. I've installed Node.js and can run "npm" from the command line. I've also installed the NodeJS plugin v0.2.1 for Jenkins. I then went into the Configure System section of Jenkins, scrolled down to NodeJS installations, clicked on Add NodeJS button, gave "NodeJS" as the name, and "C:\Program Files\nodejs" as the path to the installation

Grunt on Windows 8: &#39;grunt&#39; is not recognized

由 陌路散爱 提交于 2019-11-26 09:24:46
问题 I\'m having a problem running Grunt from the command line on my Windows 8 machine. My research indicates the most common solution is to install grunt-cli, since Grunt is no longer global. I also need to make sure I actually install the Grunt task runner, since that\'s not installed with grunt-cli. Other solutions point to the PATH system environment variable, but that appears to be pointed as I\'d expect to: C:\\Users[username]\\AppData\\Roaming\\npm Having done all that, I\'m still getting a
订阅 grunt-cli