Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for coffee-script source maps #179

Closed
MaksJS opened this issue Mar 12, 2013 · 15 comments
Closed

Support for coffee-script source maps #179

MaksJS opened this issue Mar 12, 2013 · 15 comments

Comments

@MaksJS
Copy link

MaksJS commented Mar 12, 2013

Hi everyone, great to see that this module isn't dead already :)
That would great if you could generate source maps with coffee-script files at compile. It's now available with CS 1.6. Maybe it's more a snockets enhancement ?

@dustyburwell
Copy link
Collaborator

Unfortunately, for the time being Connect-Assets is heavily dependent on Snockets and all compilation goes through it. For that reason, I highly doubt there will be a 2.x version of CA that supports this. A lot of things are changing with v3, so I'll add it to that milestone for now and we can evaluate if it'll make it in.

@adunkman
Copy link
Collaborator

Yes! Source maps are awesome.

That's about all I know about source maps. Do you have a good resource to educate me? :)

@MaksJS
Copy link
Author

MaksJS commented Mar 13, 2013

@adunkman Yep :) have a look at http://www.html5rocks.com/en/tutorials/developertools/sourcemaps/

Imagine, when a Javascript error is thrown, instead of getting Javascript line number, you'll get the line number of your Coffeescript file. That's really useful for debug

@einhorndesign
Copy link

As a developer, who uses connect-assets, I'd find this incredibly useful. As it stands debugging is quite a pain.

@adunkman
Copy link
Collaborator

adunkman commented May 7, 2013

Would it be safe to say that source maps should only be served when in development, not in production?

@williamcoates
Copy link

Sounds good to me having it dev only

@ansman
Copy link

ansman commented Jul 12, 2013

@adunkman For me it's quite the opposit.

In production I usually minify my javascript making debugging impossible.
If I could debug my coffee source in production that would be amazing!

@christiangenco
Copy link

Bump.

@adunkman
Copy link
Collaborator

adunkman commented Aug 8, 2013

connect-assets depends on snockets for this sort of thing—and source maps are included in what's being tackled for the next release. See pthrasher/snockets#43 for more information.

@adunkman
Copy link
Collaborator

v3 has changed slightly; it now depends on mincer — so we have a new issue link: js-kyle/mincer#82

@puzrin
Copy link

puzrin commented Aug 16, 2013

That mincer issue is outdated (architecture changed since 0.5.0), and implementation was not ideal. I'm not sure, that it can be merged. The most easy way is to wait until sprockets 3.0 released. Then it will be more clear how to port sourcemaps support to mincer properly.

@domachine
Copy link

Any news in this?

@domachine
Copy link

Seems that mincer now supports that feature. This is currently the only reason holding me back to use this.

@siboulet
Copy link

Any update on this? How to enable generating source maps in connect-assets? Seems Mincer now supports it, as mentioned by @domachine. Without source maps debugging minified assets is impossible.

@adunkman
Copy link
Collaborator

adunkman commented Jul 2, 2015

I haven’t made the time to make it happen in connect-assets, but pull requests are always welcome!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

10 participants