Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
async sourcemaps #2515
I was experimenting with async support in our project and while the implementation works the generated source maps are not really helpful i think. To me its seems they are jumping around without actually following the code . When i compare this to the source maps from https://github.com/MatAtBread/browserify-nodent i think the babel ones are lacking a little.
Does anybody else have the same issue ?
Well for me the source maps are not working well at all. At first glance it looked ok, but stepping through often results in quite weird jumps that don't follow the steps all the time...
Thanks about the nodent feedback. Is there anything else nodent gets wrong other than what you mentioned?
----- Ursprüngliche Nachricht -----
BTW I'd heavily recommend against using nodent. It gets the semantics very wrong and doesn't handle abrupt completions and iteration pausing very well.
with the online tool its also not working well. on the left i see about two pages of script and on the right the entire remaining code but the moment i scroll down past the left two pages i dont get any highlights anymore.
i am not sure how this tool works anyway, when i cluck custom it asks me for the generated source file ... so i provide my compiled js file but then it doesnt ask me for the map file.. so how can i specify my map file anyway ?
then again i just realized that our gulp/babel/exorcist flow doesn't remove the
Agreed - I see bizarre behavior with sourcemaps all the time. It's very distracting and difficult to follow when working with the Console in DevTools.
I have the same issue with debugger jumping after hitting an await line.
I think this might be related to the issue I reported: https://phabricator.babeljs.io/T6936
referenced this issue
Mar 9, 2018
@kittens Why was this closed? Was looking into an issue with debugging Babel compiled code in VS code and they also mentioned that the source maps being generated around async/await are incorrect by Babel. Is there a spec of some sort for source maps around async/await somewhere that we can compare against to verify this? microsoft/vscode#45345