In webstorm, running grunt serve from the terminal works flawlessly and presents me with a webpage. However, when I make a configuration and run that, there's an error concerning SASS to CSS compilation:
Running "concurrent:server" (concurrent) task
Warning: Running "compass:server" (compass) task
Warning: You need to have Ruby and Compass installed and in your system PATH for this task to work. More info: https://github.com/gruntjs/grunt-contrib-compass Use --force to continue.
Aborted due to warnings.
which I do not understand, as I'm using the same settings (described here)
Seems WebStorm doesn't see your terminal environment when being started from shortcut. Pleasee try editing the launcher as suggested in https://devnet.jetbrains.com/message/5513463#5513463 - does it help?
Related
I am working on an Application developed in Asp.Net with Angular.
While running my project using inetmgr, My angular is not working.
Then I checked in Task runner, Then get following error.
cmd.exe /c grunt -b "D:\DevProjects\LogisticMonitor\trunk\CcxTLM.Web" --gruntfile "D:\DevProjects\LogisticMonitor\trunk\CcxTLM.Web\Gruntfile.js" default
Running "clean:files" (clean) task
Warning: Object object has no method 'pluck' Use --force to continue.
Process terminated with code 3.
Aborted due to warnings.
I changed latest versions of all dependies in package.json. Then Build the project.
It fixed for me.
I'm using travis to test my code. Recently the grunt tasks have started to fail without no change being made to anything involved with grunt. (The new commit which is tested contains just very minor changes in two PHP files.)
Here is the part of log from travis:
$ grunt build:app
Running "typings:default" (typings) task
Warning: Cannot find any-promise implementation nor global.Promise. You must install polyfill or call require("any-promise/register") with your preferred implementation, e.g. require("any-promise/register")("bluebird") on application load prior to any require("any-promise"). Use --force to continue.
Aborted due to warnings.
The command "grunt build:app" exited with 3.
I tried to search for that warning message but couldn't find anything useful.
One more thing: When I run grunt build:app locally on my pc it works just fine.
Thanks for your time :)
I had the same problem when I started using grunt-typings. Worked locally and didn't work on my CI server. Ended up fixing it by doing what the error message suggests:
npm install bluebird
npm install any-promise
In GruntFile.js:
require("any-promise/register")("bluebird");
Update your node.js version to >v0.12. To check your version of node.js use node -v. The documentation of any-promise explains:
Node.js versions prior to v0.12 may have contained buggy versions of the global Promise. For this reason, the global Promise is not loaded automatically for these old versions. If using any-promise in Node.js versions versions <= v0.12, the user should register a desired implementation.
I've installed both the grunt-cli and grunt globally using the -g option.
However when I try and run grunt I get this error:
grunt --gruntfile /Users/a/root/config/Gruntfile.js
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:
http://gruntjs.com/getting-started
This is confusing as it seems to say that you are suppose to do a local install.
It seems contradictory actually. I clearly have a grunt file in place.
Grunt-cli is installed globally so that the grunt command is available to be run from any location on your system. Without the global installation, you would need to rely on somewhat abstract methods of running local grunt installs (npm run-script and friends), which are clunky for this use.
The entire point of the global install is only to load and run a local Gruntfile.js using the locally installed version of Grunt. The error message indicates this:
either a Gruntfile wasn't found or grunt hasn't been installed locally to your project.
In other words, to run Grunt, you need to create a Gruntfile.js and you must have a local copy of Grunt installed to your project alongside the file. The CLI is just there to kick off the process without troublesome fiddling.
I am following the installation guidelines as described on mean.js.org Everything seemed to install fine. I have all prereqs installed. I ran npm install after cloning the github repo and then tried to run grunt and I didnt get any errors however It seems to just be stalling on the command line. Last message on the command line is the "debugger is running on port 5858" and then it just sits there.
After some time the message [nodemon] watching 51,839 files - this might cause high cpu usage. To reduce use "--watch" comes up. I am on windows 10 and have all the latest versions of node,npm,grunt and mean.js. I am running the command line as admin.
Mean.js should be running on localhost:3000 but it is not.
This is intended.
There is an application invoked by the grunt command and running in background, watching your files for changes. In default configuration: nodemon and grunt-watch.
This will execute specific tasks based on the files you edited, such as linting JS files or compiling LESS files.
The cmd will probably show something when you edit files in the projects directory.
roys-mbp:gucci Filthy$ grunt serve
Running "serve" task
Running "clean:server" (clean) task
Running "concurrent:server" (concurrent) task
Warning: Running "sass:server" (sass) task
Warning: /Users/Filthy/Documents/gucci/app/styles/main.scss:4: error: file to import not found or unreadable: '../../bower_components/bootstrap-sass-official/vendor/assets/stylesheets/bootstrap.scss'
Use --force to continue.
Aborted due to warnings.
Execution Time (2014-05-07 07:06:54 UTC)
loading tasks 3ms ▇▇▇▇▇▇▇▇▇▇▇▇▇ 27%
sass:server 7ms ▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ 64%
Total 11ms Use --force to continue.
Aborted due to warnings.
Try running 'bower install' to install your dependencies.
I had the same problem, the path to bootstrap.scss was wrong.
Did you use the webapp generator?
Change the line 4 in main.scss from
'../../bower_components/bootstrap-sass-official/vendor/assets/stylesheets/bootstrap.scss'
to
'../bower_components/bootstrap-sass-official/vendor/assets/stylesheets/bootstrap.scss'
or to whatever the path to the bootstrap.scss may be.
I had the same problem. I was thinking npm and bower dependencies was installed, but the installation didn't end.
To fix it:
npm install
bower install
That fixed my problem.
There is a problem in your sass file, use this source
#import "bootstrap-sass-official/assets/stylesheets/_bootstrap.scss";
Open cmd promt
go to the project folder
type -> bower install and enter
it will install bower components
and show option to which version need to be installed
then the problem solved
Its working fine for me try it.....