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

Source Maps #3

Open
redswoop opened this issue Nov 9, 2012 · 3 comments
Open

Source Maps #3

redswoop opened this issue Nov 9, 2012 · 3 comments

Comments

@redswoop
Copy link

redswoop commented Nov 9, 2012

Would it be possible to run the compiler with the equiv of -sourcemaps, and then somehow store that output in a way that the source map URL would be able to refer back to sourcemap content without having to do a actual URL fetch? (i.e. base64 encoding the sourcemap and using it as the sourcemap URI?)

@redswoop
Copy link
Author

redswoop commented Nov 9, 2012

Aha! Source Maps can actually be expressed as inline data url's.

@niutech
Copy link
Owner

niutech commented Nov 16, 2012

I don't know if the original TS compiler in typescript.js can generate sourcemaps, and even if it can, it will definitely decrease performance. And where should the sourcemaps be stored?

Personally, I think that the outputted JS code is readable enough and can be easily tracked in any inputted TS file.

@matthewoates
Copy link

Typescript now supports source mapping. Sure, you can easily debug without mapping. This takes time and is tedious. Engineers don't like tedium. (or at least they shouldn't)

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

No branches or pull requests

3 participants