Issues with sourceMaps and browserify-shim about coffeeify

[jnordberg]

What's the issue?

[lagoasoft-lucasschmidt]

Sorry,
the source-maps are simply not matching with the original files. They move a few lines.

Sorry, I will attempt to debug exactly the lines and see if I can find more info, the JSON data is just too freaking huge, so I am taking a bit too long.

But for now my question would be: should it work properly? Run coffeeify with sourceMaps and then browserify-shim, or is there any other config?

I will post it later after I can analyze the sourceMap data, but in Chrome of all devs, the mapping is simply wrong.

[lagoasoft-lucasschmidt]

Ok, I did some analysis here.

If I put the breakpoint in the first line of a method, it means I am putting a breaking point in the method definition.

So, the actual breakpoint is always 1 line before the actual coffee line.

The real issue is to detect all versions of the tools, since I am using cartero that uses parcelify (https://github.com/rotundasoftware/parcelify) to call browserify for each page that I have.

Browserify version: 3.44.0
Coffeeify tried latest version. (I tried the one before that as well)

Problem is that I tried removing browserify-shim and still, the mapping went wrong for about 1 line as well.

So, this may be related to something else, and not browserify-shim.

[jnordberg]

Ok, that's quite the stack you got there :) If you can reduce the issue down to a reproducible example with just coffeify and another transform I might be able to help.

Otherwise maybe someone with some experience with the modules you are using can chime in

[lagoasoft-lucasschmidt]

Sure, I will do that, I just initially though the issue was with coffeeify and browserify-shim, but I guess I was wrong. I will do some more investigating, and if I find any issues regarding this module I let you guys know.

If you guys know any known issues, let me know.

Just to add, I was able to limit the stack by reproducing the problem using this:

browserify src/views/pages/dashboard/dashboard.coffee -g coffeeify -g browserify-shim -g browserify-plain-jade -o bundle.js --debug

latest version of all these tools

Thanks.

[lagoasoft-lucasschmidt]

Is this the cause of the issue?
browserify/browserify#322

[juriejan]

I'm experiencing the same issue. Ever figure out what might be causing it, or found a solution?

[lagoasoft-lucasschmidt]

Well @juriejan , what I did was simply avoid using coffee sourceMaps, instead, just plain javascript.

I changed my build system, so I dont use coffeeify anymore. I transform to js using grunt, and then grunt triggers a job that does browserify stuff. It got pretty complex, but in the end, I think this is best, since its actually faster than the original plan.

In the browser, I am able to view the js files as the source maps, so its no big deal.

edit: I simply dont remember if I found a guilty party, probably not, I did try a lot to fix it, but it got to the point where speed mattered more, so I focus on that.