meteorhacks / zones

Zone.js integration for meteor
MIT License
30 stars 11 forks source link

Is it normal behaviour "@debugger eval code:2:3" in reporters.js:67 ? #55

Open lc3t35 opened 10 years ago

lc3t35 commented 10 years ago

When i launch an error in console, i have a strange return message, is it the normal behaviour ?

setTimeout(function(){
  throw new Error('Hello Error');
}, 100);
140
"Error: Hello Error
@debugger eval code:2:3                      reporters.js:67
"

The error is well displayed in ui - errors - events :

 App Loaded into Browser
after 32 ms

Inside event "readystatechange" of "Unknown Element"

after 51 ms

Inside "setTimeout"

after 21.60 secs

Inside "setInterval"

after 114 ms

Inside "setTimeout"

Error: Hello Error
Stack:

@debugger eval code:2:3
arunoda commented 10 years ago

Actually. In reality, this will get much better. This is since, you've throws the error by yourself using the console.

On Thursday, September 11, 2014, Laurent Roger notifications@github.com wrote:

When i launch an error in console, i have a strange return message, is it the normal behaviour.

setTimeout(function(){ throw new Error('Hello Error'); }, 100); 140 "Error: Hello Error @debugger eval code:2:3 reporters.js:67 "

The error is well displayed in ui - errors - events :

App Loaded into Browser after 32 ms

Inside event "readystatechange" of "Unknown Element"

after 51 ms

Inside "setTimeout"

after 21.60 secs

Inside "setInterval"

after 114 ms

Inside "setTimeout"

Error: Hello Error Stack:

@debugger eval code:2:3

— Reply to this email directly or view it on GitHub https://github.com/meteorhacks/zones/issues/55.


Arunoda Susiripala I curate Meteor Weekly - Check it out! http://meteorhacks.com/meteor-weekly/?utm_source=email-footer&utm_medium=email&utm_campaign=meteorweekly