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

New Stab at Source Maps #2256

Closed
jashkenas opened this issue Apr 12, 2012 · 8 comments
Closed

New Stab at Source Maps #2256

jashkenas opened this issue Apr 12, 2012 · 8 comments

Comments

@jashkenas
Copy link
Owner

.... from @itrelease:

https://github.com/itrelease/coffee-script/commit/4d5a352d10ea331431608e6024434ff359707251

@mark-hahn
Copy link

It was just pointed out in the forum that Google now has full support for source maps in chrome's inspector. Is the implementation of source maps in this thread compatible? Is this implementation in the latest coffeescript build?

I'm very excited about this for obvious reasons.

@brian428
Copy link

Just wondering if there is any update on this, since Chrome has now supported it for nearly six months and Firefox support is now in the nightly build. Obviously this would make debugging a lot easier, but I haven't seen or heard anything further on the source maps feature here or on the mailing list. Thanks.

@mpj
Copy link

mpj commented Nov 10, 2012

"Michael Ficarra’s successful kickstarter to create a “better CoffeeScript compiler” is already paying some huge dividends to the backers with source maps."
http://ryanflorence.com/2012/coffeescript-source-maps/

@jrozner
Copy link

jrozner commented Nov 27, 2012

What's the status of this ticket? Is there not interest in adding in sourcemap generation? Should we be using Coffeescript Redux if we want it instead? Or are you waiting for a solution that doesn't depend on mozilla's library?

@jashkenas
Copy link
Owner Author

  • There is interest.
  • CoffeeScript Redux already has them working well. Give it a try if you'd like to use them today.
  • For the curious, there's a new fork of the original compiler that's getting pretty far along on implementing source maps (with the aim of eventually pursuing code coverage and other goals): https://github.com/benbria/coffee-script/commits/master

@JamesMaroney
Copy link

@jashkenas I have tried using CoffeeScript Redux for our quite large CoffeeScript codebase -- and while the sourcemaps are absolutely awesome, they are not worth the compromises we have to make in our CS code in order to use the new compiler (e.g. michaelficarra/CoffeeScriptRedux#153 and michaelficarra/CoffeeScriptRedux#121)

What is the relationship between you and CoffeeScript Redux. Is it poised to become the future "CoffeeScript" compiler, or is this a splintering - and CoffeeScript will aim to provide it's own implementation of sourcemaps?

If it's a splintering, then I'd prefer to stay with the more flexible sytnax.

@michaelficarra
Copy link
Collaborator

@JamesMaroney: those issues will be fixed shortly. See the 2.0 roadmap in the wiki.

@JamesMaroney
Copy link

@michaelficarra ok, that's awesome. linking to that from your readme would really help those of us that are trying to figure out your vision for CSRedux. Many of us have very large codebase investments in CS and just want to make sure we are making proper decisions moving forward.

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

8 participants