Stack trace does not show column when exception occurs.

[fmmontas]

Whenever a javascript exception occurs the stack trace only contains the line number and not the column, ex. 'path/to/file/someFile.js:56' where 56 is the line number. Without the column number source maps will not currently work. Given an exception occurs 'path/to/file/someFile.js:56:11' where line number is 56 and column number is 11 seems like the common format.

[NickClark]

👍 Running tests in Karma with source maps, and I really like that PhantomJS gives better error messages for failures (TypeError: 'undefined' is not a function (evaluating 'calc.add()') vs Chrome's plain TypeError: undefined is not a function), but unfortunately, no column number breaks Karma's ability to use source maps

[samu]

👍

[jtomaszewski]

+1 - currently I need to use Chrome in Karma, because sourcemaps don't work in PhantomJS :(

[leonardfactory]

👍

[dtryon]

+1

[alexbuijs]

+1

[andras-tim]

+1

[decates]

+1

[supersonicclay]

+1 this is essential for running unit tests with Karma and PhantomJS

[danieljsinclair]

+1

[axelpale]

+1

[matthauck]

👍

[matthauck]

Hmm. Looks like this may not be a phantomjs issue anymore. Just updated to phantomjs-prebuilt 2.1.5, and column numbers are now present!

[WolfgangKluge]

Hmm, I've still the same problem with phantomjs 2.1.1 (phantomjs-prebuilt 2.1.14) on windows.

I see phantomjs://code/test.js:4 in global code when I execute the script

setTimeout(function () {
    phantom.exit();
}, 0);
throw '';

Still no column numbers (and therefore no chance to get source maps to work correctly)..

[JoshSchreuder]

Hmm, I've still the same problem with phantomjs 2.1.1 (phantomjs-prebuilt 2.1.14) on windows.

Same here. If I run the tests via Karma in Chrome / Firefox the stacktrace uses sourcemaps correctly.

[dreadwail]

@vitallium I don't think this is fixed, so any chance of re-opening it?

[rmartins90]

+1