Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

I cannot run "grunt serve" #30

Closed
thucxuong opened this issue Jan 14, 2014 · 8 comments
Closed

I cannot run "grunt serve" #30

thucxuong opened this issue Jan 14, 2014 · 8 comments

Comments

@thucxuong
Copy link

I catched this error when running grunt serve command.
FileError: '../bower_components/bootstrap/less/bootstrap.less' wasn't found in app/styles/main.less on line 1, column 1:
Can you help me ?

@ptim
Copy link

ptim commented Jan 15, 2014

I'm experiencing this, too..

@ptim
Copy link

ptim commented Jan 15, 2014

The entire app/bower directory was missing.. tracked back to the message:

I'm all done. Running bower install & npm install for you to install the required dependencies. If this fails, try running the command yourself.

Running these two commands manually sorted the issue out for me with grunt serve (though running grunt fails with niggling jshint errors)

Thanks!

@thucxuong
Copy link
Author

Yeah, you're right,I give it a try. I'll tell u if it's the case.

Thanks.

@jonahvsweb
Copy link

Run grunt build & grunt server to avoid the jshint errors.

@joshuapekera
Copy link

Just run bower install that will install all your bower components that are speced in the bower.json file and mapped in the .bowerrc file. Then run grunt serve

@andrewcarreiro
Copy link

There appears to be an error in the generator. On line 156 of my gruntfile, there is:

less: {
    options: {
        paths: ['<%= config.app %>/bower_components'],
    },

However, this is incorrect. The bower_components directory does not exist inside the config.app directory, it resides beside it. I believe this block should read:

less: {
    options: {
        paths: ['bower_components'],
    },

@say2joe
Copy link

say2joe commented Aug 5, 2014

@andrewcarreiro Thank you. That was the issue. I've seen this issue in quite a few generators actually, over the past year or so... but this is the best answer for the fix!

@recurrsed
Copy link

@andrewcarreiro Thank you good man!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants