15

I have followed the steps to install mean.io, but when I browse the localhost:3000 I get a blank page and when I open the console I get a list of files pointing to the same error:

Uncaught ReferenceError: angular is not defined

my issue is something similar to this, but I re-installed bower and it didn't work I'm still getting the error.

I'm trying to install this in ubuntu 14.04

this is the screen I get:

Uncaught ReferenceError: angular is not defined

Do I need to perform some sort of modification to any script, file reference or configuration, any suggestions?

howrad
  • 1,066
  • 2
  • 12
  • 32
pedrommuller
  • 15,741
  • 10
  • 76
  • 126
  • 1
    What do you see in the Network tab? Is there a 404 for angular.js or angular.min.js? Also, you say your "reinstalled bower" but what that article instructed you to do was run "bower install" (ie. run "bower" on the command line with "install" as the parameter). Which did you do? – Marc Kline Apr 30 '14 at 22:32
  • 1
    I used bower install --allow--root, it turns out that I had blocked some urls for some bower dependencies, it's fixed for now. thanks for your comment! – pedrommuller May 07 '14 at 20:45

4 Answers4

27

I had the same problem and I solved in this way:

You need to install or reinstall "bower"

Check your bower.json file, it should look something like this:

{
"name": "mean",
"version": "0.3.0",
"dependencies": {
    "angular": "latest",
    "angular-resource": "latest",
    "angular-cookies": "latest",
    "angular-mocks": "latest",
    "angular-route": "latest",
    "bootstrap": "latest",
    "angular-bootstrap": "0.10.0",
    "angular-ui-router": "#master"
  }
}

and then run the following command:

  sudo bower install --allow-root

This will install to "Angular" in the project

Reegan Miranda
  • 2,879
  • 6
  • 43
  • 55
Christian Cruz
  • 670
  • 8
  • 9
  • 3
    It didn't even occur to me that Bower had failed to run or that my Yeoman MEAN generator hadn't run it at all. I was able to simply run "bower install" and it fixed my problem completely. – John Munsch Sep 07 '14 at 03:30
  • Thanks for the help. I didn't get this this error the previous five times I installed this. I'm still unclear as to what I did incorrectly but this solved the problem at least. – RevNoah Sep 24 '14 at 04:12
  • I think that happens when you have installed git – Christian Cruz Oct 10 '14 at 18:45
  • I got this error after I checked out the code in a new environment and needed to install bower and run bower install. Thanks for the hlep. – latj Nov 21 '14 at 01:01
2

I had the same problem but for some reason the top answer here (reinstalling bower and running sudo bower install --allow-root) didn't work for me.

However the answer form this stackoverflow thread worked -> bower command not found Basically the author there said I wasn't setting npm prefix properly and to fix that the following was required: 

$ npm config set prefix /usr/local
$ npm install -g bower
Community
  • 1
  • 1
Mukul Raina
  • 351
  • 1
  • 5
  • 14
0

note the it is bad form to install mean.io as root and as a result run bower or npm as root. We actually built processes into mean-clithat will disallow running as root. Running as root is the sure way to expose mean to more serious security issues and to "contaminating" you .npm and .bower caches with a mix of normal and root based permissions which is very frustrating for "newbies"

Lior Kesos
  • 294
  • 1
  • 5
0

If you are behind the proxy, then still problem not solved. So in order to solve it you need to include proxy-setting in .bowerrc file as

 {
  "directory": "public/lib",
  "proxy":"http://user:passwd@server:port",
  "https-proxy":"http://user:passwd@server:port"

}

Now run

sudo npm install -g bower
sudo bower install --allow-root
reenu29
  • 9
  • 1