I'd like to embed some information about the source-level lexical
environment within the source map format, so that it can take its first
baby steps towards being a Real Debugging Format(tm).
This will enable:
1. Debuggers to rematerialize the source-level environment
and their bindings (regardless if there are corresponding scopes and
bindings in the generated JS).
2. Debuggers to locate a binding's current value. This includes situations
* The binding was renamed in the compiled JS. For example, the binding is
in the original source and renamed to
* The binding does not have a corresponding binding in the compiled
recognizing that the binding was never mutated.
Here is the proposal, for your consideration:
Feel free to discuss it on this list or on the source-map-rfc pull request: