Source maps are the standardized way of defining the original source of CSS, JS and other compiled-to-the-deployed-web languages. https://github.com/h5bp/html5

Source maps are the standardized way of defining the original source of CSS, JS and other compiled-to-the-deployed-web languages. https://github.com/h5bp/html5-boilerplate/issues/820 https://github.com/h5bp/html5-boilerplate/issues/820 In this thread I ended up proposing something very much like what Dan is saying here but realized (after Kevin Dangoor, product manager of Firefox's Developer Tools, chimed in) that indeed source maps were designed exactly for this situation, no authoring convention or filename guessing necessary. Source maps not only can point to the original sources, but can translate between minified css and fully formatted Sass with comments, and developer tools can identify the mapping. As for how ready this is, CSS source map plumbing is in both Firefox and WebKit, though they are not totally complete. I believe FF has a Google Summer of Code student working on the feature: https://wiki.mozilla.org/DevTools/Features/CSSSourceMap https://wiki.mozilla.org/DevTools/Features/CSSSourceMap Just because its relevant: all the source map projects: https://github.com/ryanseddon/source-map/wiki/Source-maps:-languages,-tools-and-other-info https://github.com/ryanseddon/source-map/wiki/Source-maps:-l...