-
Notifications
You must be signed in to change notification settings - Fork 36
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 do not preserve history #67
Comments
eventualbuddha
added a commit
to decaffeinate/decaffeinate
that referenced
this issue
Mar 8, 2016
I tried to combine the sourcemaps into a single one with sorcery, but ran into this: Rich-Harris/sorcery#67.
This is a HUGE bug. Thanks for pointing it out. I'll be giving it a shot in my own fork. edit: Actually, I bet @Rich-Harris is aware of this, but I think sorcery ought to support it. :) |
The I've got a solution on the way. Writing some tests, currently. 🙂 |
10 tasks
Any news on this one? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have been trying to use sorcery to combine source maps for transformation steps in decaffeinate and ran into what I believe to be a bug in sorcery. I still have a somewhat weak understanding of source maps so I may simply be wrong, but I thought I'd ask.
Here's a file that, when saved as
bug.js
and run withnode bug.js
afternpm install sorcery
to install sorcery, will illustrate the issue:So we can see that the output map has lost all the mappings from the babel map and instead simply uses the mappings from the second map as-is. I would expect that the output should be essentially the same as the babel mappings but shifted by one line, so essentially
;AAAA,IAAI,IAAI,CAAJ;;AAEJ,SAAS,CAAT
.The text was updated successfully, but these errors were encountered: