In the JS ecosystem, where nearly everything published is pre-built, I think it’s time to consider tools for sourcemap’ed git blame or similar. Without leaving

In the JS ecosystem, where nearly everything published is pre-built, I think it’s time to consider tools for sourcemap’ed git blame or similar. Without leaving my editor I can place my cursor on any line in my own projects, or any line in a clone of a dependency, and get instantaneous information about the last change to that line. The same change in the published package has no way of tracing that information. The usual rigmarole from there is search the package name > no really I want the GitHub link, not NPM > what on earth does the source code structure even look like? > is it even in this repo? > FFS GitHub search is more paternalistic and useless than Google/Bing > drink a whiskey, sleep on it > a full day poring over all of the internals of the dependency, probably a PR to fix something horrifying discovered along the way > shit I should have taken more notes > PR with a version bump in package.json to your fork with the fix, with no comments because this is JSON fuck comments!