Bug introduced in Version 0.11 and up about mochify.js HOT 9 CLOSED

I wish I had a better understanding of why this is happening but I just know that it is.

from mochify.js.

Hahahaaaaa! Sorry, but that is soooo funny. Hahaha!
Let me explain, so you can laugh about this as well:

There was a feature in Phantomic to filter stack traces and map them back to the original sources using source maps. This has moved into a separate module (https://github.com/mantoni/source-mapper.js) and is now used to filter node output as well (e.g. mochify --node).

With the move into the new project I found more cases where the URLs had to be mapped for node and made the regular expression more generic. A bit too generic as it seems. Your console output gets changed because http://localhost:9001 is replaced with jquery.js:2312 using a source maps lookup. I don't think your variable values have changed.

from mochify.js.

Hum interesting might want to clean that up some more if you can, cause it
messed me up for about a day. Let me see if the test passes now that i've
got it working.

On Fri, Jul 25, 2014 at 12:10 PM, Maximilian Antoni <
[email protected]> wrote:

Hahahaaaaa! Sorry, but that is soooo funny. Hahaha!
Let me explain, so you can laugh about this as well:

There was a feature in Phantomic to filter stack traces and map them back
to the original sources using source maps. This has moved into a separate
module (https://github.com/mantoni/source-mapper.js) and is now used to
filter node output as well (e.g. mochify --node).

With the move into the new project I found more cases where the URLs had
to be mapped for node and made the regular expression more generic. A bit
too generic as it seems. Your console output gets changed because
http://localhost:9001 is replaced with jquery.js:2312 using a source maps
lookup. I don't think your variable values have changed.

—
Reply to this email directly or view it on GitHub
#24 (comment).

Mikela

from mochify.js.

Yeah looks like the tests are passing now even though the output is messed
up. For now this is going to keep me from updating.

On Fri, Jul 25, 2014 at 12:15 PM, Mikela Clemmons [email protected]
wrote:

Hum interesting might want to clean that up some more if you can, cause it
messed me up for about a day. Let me see if the test passes now that i've
got it working.

On Fri, Jul 25, 2014 at 12:10 PM, Maximilian Antoni <
[email protected]> wrote:

Hahahaaaaa! Sorry, but that is soooo funny. Hahaha!
Let me explain, so you can laugh about this as well:

There was a feature in Phantomic to filter stack traces and map them back
to the original sources using source maps. This has moved into a separate
module (https://github.com/mantoni/source-mapper.js) and is now used to
filter node output as well (e.g. mochify --node).

With the move into the new project I found more cases where the URLs had
to be mapped for node and made the regular expression more generic. A bit
too generic as it seems. Your console output gets changed because
http://localhost:9001 is replaced with jquery.js:2312 using a source
maps lookup. I don't think your variable values have changed.

—
Reply to this email directly or view it on GitHub
#24 (comment).

Mikela

Mikela

from mochify.js.

Sorry about that. I'll see if I can implement some more clever matching.

from mochify.js.

No sorry necessary still think your a decent package maintainer link me the place you do this and i might make a PR

from mochify.js.

It's here: https://github.com/mantoni/source-mapper.js

from mochify.js.

0.11.3 should fix this problem.

from mochify.js.

best

On Fri, Jul 25, 2014 at 1:49 PM, Maximilian Antoni <[email protected]

wrote:

0.11.3 should fix this problem.

—
Reply to this email directly or view it on GitHub
#24 (comment).

Mikela

from mochify.js.