All AngularJS runtime errors refer to angular.js - no helpfull stack trace

Question

I have started a new AngularJS project - and this time something strange is happening. Whenever I get an error in the browser's console, it references to the angular.js file. I don't know what's different with this app from all my others - maybe the AngularJS version (1.6.4). Or the fact that I'm using controllerAs syntax?

For example - if I try the following in my main controller:

vm.notdefined.somevalue = "this should give an error";

I don't get a console error with the line of code in my controller, but with a line in angular.js:

angular.js:14525 TypeError: Cannot set property 'somevalue' of undefined(…) ""

It would be ok for me if I could trace back the error from the stack trace - but also the stack trace does not contain any information on the position of the error in my project.

Community · Accepted Answer · 2017-05-23 12:02:45Z

1

The error is thrown where it appears. vm.notdefined.somevalue is a part of ngControllerinstance. In the moment your controller get parsed the error is thrown. This happends inside AngularJS kernel logics. You could check the stack trace for debugging. It should lead you to your controller function. You could also use breakpoints on your code e.g. by using chrome debugger. All in all this will lead you to the origin of this error.

For more information about debugging please check this answer: How can I get more stacktrace in AngularJS

The error message is quite clear: vm.notdefined is undefined. Try:

vm = this;
vm.notdefined = {
   somevalue: "this should give an error"
}

edited May 23, 2017 at 12:02

CommunityBot

11 silver badge

answered Apr 3, 2017 at 23:13

lin

18.5k4 gold badges66 silver badges88 bronze badges

Sign up to request clarification or add additional context in comments.

5 Comments

ESP32 Over a year ago

I create this error intentionally! I want to demonstrate, that the error is refered to a line in angular.js, instead of the correct position in my controller file.

lin Over a year ago

@Gerfried it is correct, that the error is thrown in angular.js file because vm is an instance of angular-controller. It is the correct "position/line" of code where the error is thrown. What's wrong with it? And what is your question so?

ESP32 Over a year ago

It's difficult to debug errors. I also tried with $scope instead of vm - same behaviour. This is new to me - in my other projects the error shows up in the controller.

lin Over a year ago

@Gerfried This is not a problem at all. Check the stack trace for debugging. What is your question so? What kind of answer do you expect or what kind of answer would you mark as right?

ESP32 Over a year ago

Ok, I understand - but in the stack trace there is no information on my controller file as well. I will add it to my question

ESP32 · Accepted Answer · 2017-05-22 10:26:06Z

0

Shame on me - I missed to click on the three dots to expand the error message:

Not sure why I have to do this sometimes and other times I get the error stack in the immediate stack.

answered May 22, 2017 at 10:26

ESP32

8,7732 gold badges46 silver badges71 bronze badges

Collectives™ on Stack Overflow

All AngularJS runtime errors refer to angular.js - no helpfull stack trace

2 Answers 2

5 Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

5 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related