Unreadable error message when a module is missing

[mgol]

Chrome clips long error messages with no way to get to their full text making most Angular "unfound dependency" messages completely useless. An example I stumbled upon now:

Uncaught Error: [$injector:modulerr] Failed to instantiate module mgol due to:
Error: [$injector:modulerr] Failed to instantiate module mgolCatchLinks due to:
Error: [$injector:modulerr] Failed to instantiate module mgolRoute due to:
Error: [$injec...<omitted>...1)

[CWSpear]

I've never seen <omitted> before. Can you click on it to expand it at all? Are you using the dev (unminified) or the production (minified) version of the code?

[mgol]

@CWSpear This text is not clickable. I've just checked that the problem doesnt' exist in Chrome stable (31) but it has existed in Canary for a long time now, not sure if it's going to land in 32 or 33.

I'm using the non-minified Angular version.

[CWSpear]

@mzgol Strange. I see it, too on Canary. You should open a bug with Blink/Chromium/Canary/Chrome or whomever you need to on that end, as that seems like it may be a bug/unintended (or otherwise should be reversed).

[IgorMinar]

Can someone file a bug with chromium please and cross-reference it here. I wonder if this is intentional change or not.

[mgol]

@IgorMinar See http://crbug.com/331971

[mgol]

Note: the change has already propagated to Chrome stable, now the clipped message is unavoidable. :(