I was following a tutorial on mean.io, and in it, i had to install yo angular
after sometime everything was installed and finally the i had to run `grunt serve'
then this error/warning comes
mukund#mukund-ThinkPad-Edge-E431:~/MeanApp/client$ grunt serve
Running "serve" task
Running "clean:server" (clean) task
>> 0 paths cleaned.
Running "wiredep:app" (wiredep) task
Running "wiredep:test" (wiredep) task
Running "wiredep:sass" (wiredep) task
Running "concurrent:server" (concurrent) task
Warning: Running "compass:server" (compass) task
Warning: Command failed: /bin/sh -c compass --version
/bin/sh: 1: compass: not found
Use --force to continue.
Aborted due to warnings.
Execution Time (2015-07-16 10:01:13 UTC)
loading tasks 10ms ▇▇▇▇ 12%
loading grunt-contrib-compass 33ms ▇▇▇▇▇▇▇▇▇▇▇▇▇ 40%
compass:server 38ms ▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ 46%
Total 82ms Use --force to continue.
Aborted due to warnings.
Execution Time (2015-07-16 10:01:12 UTC)
loading tasks 10ms ▇ 1%
loading grunt-contrib-clean 10ms ▇ 1%
clean:server 9ms ▇ 1%
wiredep:app 185ms ▇▇▇▇▇▇▇▇ 24%
wiredep:test 10ms ▇ 1%
wiredep:sass 12ms ▇ 2%
loading grunt-concurrent 9ms ▇ 1%
concurrent:server 515ms ▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ 67%
Total 766ms
mukund#mukund-ThinkPad-Edge-E431:~/MeanApp/client$
I followed this tutorial https://www.youtube.com/watch?v=OhPFgqHz68o
Ans when i ran with this command grunt serve --force
I got the required page # htttp://localhost/9000/#/ page with without any style
You need to install compass. It is used by the SASS which is included in the angular yeoman generator.
If you have ruby installed you can do.
gem install compass
And don't use --force ever. Its not really meant for all the cases but grunt throws it for every error/warning except fatal errors.
Related
After cloning my Ionic React project to my server, I ran npm install and all dependencies were installed as expected.
But when I tried to build my app running sudo ionic build --verbose, it tooks much more time than usual and ended like this :
eslint:lint-result-cache Persisting cached results: /var/www/html/ms-users-front/node_modules/.cache/.eslintcache +0ms
eslint:cli-engine Linting complete in: 4827ms +48ms
//It stay here for at least 10min before to failed while it tooks 1min in my local machine.
The build failed because the process exited too early. This probably means the system ran out of memory or someone called `kill -9` on the process.
[ERROR] An error occurred while running subprocess react-scripts.
react-scripts build exited with exit code 1.
Re-running this command with the --verbose flag may provide more information.
ionic:utils-process onBeforeExit handler: 'process.exit' received +0ms
ionic:utils-process onBeforeExit handler: running 1 functions +1ms
ionic:utils-process processExit: exiting (exit code: 1) +44ms
My server is an ec2 instance with httpd installed and everything was working great before I tried to build a new version yesterday.
With exactly the same process, the app is building perfectly on my local machine...
I tried npm update, delete eslint cache, and build but without success.
I tried to downgrade Typescript to 4.1 because I had a warning saying that Typescript should be >4.5 and it was 4.7. But after some tests on local, it looks like this has no incidence on the build process.
I'm totally stuck and I absolutly don't know what to try.
I'm using Zeppelin 0.70. I can build zeppelin from git source. when i trying to start zeppelin on that port 8000 by using below command, it works good.
./zeppelin-daemon start
But It won't work after grunt serve command on the port 9000, but it started good and it shows web socket disconnected error.
[root#sandbox zeppelin-web]# ./grunt serve
Running "serve" task
Running "clean:server" (clean) task
Cleaning .tmp...OK
Running "wiredep:app" (wiredep) task
Running "wiredep:test" (wiredep) task
Running "concurrent:server" (concurrent) task
Running "copy:styles" (copy) task
Copied 16 files
Done, without errors.
Execution Time (2017-02-24 05:51:45 UTC)
loading tasks 277ms ▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ 91%
copy:styles 28ms ▇▇▇▇▇ 9%
Total 305ms
Running "postcss:dist" (postcss) task
>> 16 processed stylesheets created.
Running "connect:livereload" (connect) task
Started connect web server on http://0.0.0.0:9000
Running "watch" task
Waiting...
I got log in console;
XMLHttpRequest cannot load http://localhost:8080/api/security/ticket. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://localhost:9000' is therefore not allowed access. The response had HTTP status code 404.
Where do i change 8080 to 8000.
Please tell me how do i resolve this issue.
I think grunt was substituted with npm in 0.7 release, so could you try npm run dev command?
Update: There's ongoing issue under ZEPPELIN-2154 related to it. In order to fix it in your case you could remove 3 lines in here of if statement and substitute it with port = 8000; in your source code. it could be temporary fix until patch is filed to make it configurable.
I'm building a project on a yeoman angular-fullstack generator. It's been a quite a while and the landing page was correctly loading after running grunt serve task.
I really don't know what I've done but now when I run grunt serve I see ERR_CONNECTION_REFUSED message in chrome first and then the landing page loads normally(about 5 seconds after ERR_CONNECTION_REFUSED message)
This makes my e2e tests crash.
found some issues on github about grunt-concurrent downgrading and disabling livereload but nothing helps..
This is the log. As you see express server has to start listening before open server and watch tasks( newly created fullstack-generator does that so it works correctly)
Running "serve" task
Running "clean:server" (clean) task
>> 1 path cleaned.
Running "env:all" (env) task
Running "concurrent:pre" (concurrent) task
Running "ngconstant:app" (ngconstant) task
Creating module serviceboxApp.constants at client/app/app.constant.js...OK
Done, without errors.
Execution Time (2016-02-26 00:40:08 UTC)
loading tasks 302ms ▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ 85%
loading grunt-ng-constant 34ms ▇▇▇▇ 10%
ngconstant:app 19ms ▇▇ 5%
Total 356ms
Running "concurrent:server" (concurrent) task
Running "newer:babel:client" (newer) task
Running "babel:client" (babel) task
Running "newer-postrun:babel:client:1:/Users/apple/Desktop/dev/servicebox/node_modules/grunt-newer/.cache" (newer-postrun) task
Done, without errors.
Execution Time (2016-02-26 00:40:09 UTC)
loading tasks 312ms ▇▇▇▇▇▇▇ 15%
newer:babel:client 36ms ▇ 2%
loading grunt-babel 415ms ▇▇▇▇▇▇▇▇▇ 20%
babel:client 1.2s ▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ 61%
Total 2s
Running "injector:scripts" (injector) task
Missing option `template`, using `dest` as template instead
Injecting js files (33 files)
Running "injector:css" (injector) task
Missing option `template`, using `dest` as template instead
Injecting css files (9 files)
Running "wiredep:client" (wiredep) task
Running "postcss:dist" (postcss) task
Running "express:dev" (express) task
Starting background Express server
Debugger listening on port 5858
[TypeError: Cannot read property 'Kerberos' of undefined]
Running "wait" task
>> Waiting for server reload...
Done waiting!
Running "open:server" (open) task
Running "watch" task
Waiting...
Express server listening on 9000, in development mode
finished populating users
finished populating quotes
finished populating poviders
You have TypeError that is preventing your code from running properly. [TypeError: Cannot read property 'Kerberos' of undefined]
You don't know JS explains that a TypeError "implies that Scope resolution was successful, but that there was an illegal/impossible action attempted against the result."
So you need to go back to where you are calling Kerberos and resolve the TypeError
I've been looking through error reports all day and re-reading posts on here and error reports on GitHub and not finding an answer to my problem.
Error
Running "concurrent:server" (concurrent) task
Warning: >> Local Npm module "grunt-contrib-compass" not found. Is it installed?
Warning: Task "compass:server" not found. Use --force to continue.
Aborted due to warnings.
Execution Time (2015-02-18 20:46:22 UTC)
loading tasks 3ms ▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ 75%
Total 4ms Use --force to continue.
Aborted due to warnings.
Execution Time (2015-02-18 20:46:21 UTC)
wiredep:app 137ms ▇▇▇▇ 7%
concurrent:server 1.7s ▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ 91%
Total 1.8s
What I have Tried
Since the install couldn't find it to install it the first time, I reinstalled using bower install --save
After that I can't get anything to work.
Here is a copy of my Grunt.js
https://gist.github.com/ddavisgraphics/8fc9bb3958317f1fd06b
bower.json
https://gist.github.com/ddavisgraphics/d0828b048e2ac4543758
I'm a grunt newbie. My PC runs Windows 7 x64.
I followed the Yeoman tutorial (on the Yeoman site) and I did not change anything in any of the generated files. Then, I ran
grunt serve
When I change any html file, the grunt process is instantaneous, but when I modify one of the .js or .css files, the process is insanely slow. When I hit save, grunt notices it immediately :
>> File "app\styles\index.css" changed
But there seems to be around 4 long seconds before the next lines appear on the terminal :
Running "newer:copy:styles" (newer) task
Running "copy:styles" (copy) task
Copied 1 files
Running "newer-timestamp:copy:styles:R:\Personnel\Workspaces\web\front\plume\node_modules\grunt-newer\.cache" (newer-timestamp)
task
Running "newer-reconfigure:copy:styles:1" (newer-reconfigure) task
Running "autoprefixer:dist" (autoprefixer) task
Prefixed file ".tmp/styles/index.css" created.
Prefixed file ".tmp/styles/main.css" created.
Done, without errors.
Execution Time (2014-03-21 00:00:19 UTC)
loading tasks 6ms ■■■■■ 9%
newer:copy:styles 9ms ■■■■■■■■ 14%
copy:styles 7ms ■■■■■■ 11%
newer-timestamp:copy:style...odules\grunt-newer\.cache 3ms ■■■ 5%
autoprefixer 1ms ■ 2%
autoprefixer:dist 39ms ■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■ 59%
Total 66ms
... Reload .tmp\styles\index.css ...
... Reload .tmp\styles\main.css ...
Completed in 4.463s at Fri Mar 21 2014 01:00:20 GMT+0100 (Paris, Madrid) -
Waiting...
I'm confused. grunt says it took him 66ms total to run the tasks, but then it says that it took him 4.463s to complete the whole process.
What did I did wrong ? The build is clean, I did nothing else than
yo angular
To scaffold the app... Any idea ?
edit :
spawn: false
Solved my problem. Thanks to the one who brought that up. Even if I use Gulp or webpack nowadays.
There is a spawn option that sometimes make things faster --and also more prone to failing apparently.
From the documentation:
Whether to spawn task runs in a child process. Setting this option to
false speeds up the reaction time of the watch (usually 500ms faster
for most) and allows subsequent task runs to share the same context.
Not spawning task runs can make the watch more prone to failing so
please use as needed.
You would disable the spawn adding a options section inside watch in your Gruntfile.js. Something like this.
watch: {
options: {
spawn: false
},