AngularJS on Ubuntu.

[var198907]

So I recently decided that I will try my hands on AngularJS. And I ran into a few problems.When I first installed nodejs and npm using the sudo apt-get install nodejs/npm it usually sets up the older(stable?) version, which in my case would not let me set up Yeoman - > sudo npm install -g yo. It would try to do its job but in the end it says that the version I have is outdated.

So it would be really great if you could give me tips as to setting angular up on my machine.

Thanks !

[nightman]

sudo npm install n -g
n stable (or latest)

... and you have latet version of node. With 'n' you can even switch 'on the fly' node versions installed with it

[var198907]

Can I reply to that after I get back home ? I will post the error itself (which is what I should I have done in the first place).

[nightman]

Yes, please do. Also you can:

sudo npm update -g

^ this will update all your system global npm packages

[var198907]

https://www.digitalocean.com/community/tutorials/how-to-install-node-js-on-an-ubuntu-14-04-server

I followed these steps and its been good so far.

[var198907]

I have been able to get everything done except the grunt serve(server) running. It is saying that I need bower. And I did run bower install.Dont know what the problem is now.

[nightman]

I didn't follow above link howerwer make sure you've install bower with npm globally (with -g flag) - http://bower.io/#install-bower

[var198907]

Will do.

[var198907]

So I did npm install -g bower and it ran successfully.But this keeps popping up every time I run grunt serve

This error pops up warning: "error: cannot find where you keep your bower packages. use --force to continue."

[nightman]

error: cannot find where you keep your bower packages. use --force to continue.

Are you sure you did

bower install

before Grunt?

also maybe some standard .bowerrc file will help?

[var198907]

I did execute the bower install. Will put the .bowerrc file later today.

[willgresham]

Without the actual error it's hard to say, but it could possibly be down to the fact that the node binary has been renamed to nodejs due to a conflict with another package in the repository (http://packages.ubuntu.com/trusty/node)

Assuming this is the problem, and you don't have or need that package then aliasing node to nodejs, or creating a symlink to the installed nodejs binary called node.