When I was refactoring the breakpoint code, I occasionally ran into bugs that were caused by a source map not being what I expected this to be. The tool here below proved very helpful in finding these bugs: http://sokra.github.io/source-map-visualization/ By integrating this kind of visualization into the debugger, we would make it easier for other developers to analyze their source maps as well.

I guess? Is this useful to people who aren't (a) X-to-JS compiler hackers, or (b) us? Is it worth building for such a small audience?

The feature looks really cool, though as Nick says, the use case for it is very limited. When source maps are available, I believe normal users either use them to debug their (minimized) code or don't debug their code on the client side. They probably won't need to have a visualization of the mapping. Therefore I'd vote for WONTFIX. Eddy, any objections? Sebastian

(In reply to Sebastian Zartner [:sebo] from comment #2) > The feature looks really cool, though as Nick says, the use case for it is > very limited. > When source maps are available, I believe normal users either use them to > debug their (minimized) code or don't debug their code on the client side. > They probably won't need to have a visualization of the mapping. > > Therefore I'd vote for WONTFIX. Eddy, any objections? > > Sebastian Nope, fine by me.

See comment 2