Open Bug 1436580 Opened 3 years ago Updated 3 months ago
Debugger: Module support
* Debugger.Script needs an .isModule property, or maybe a .type property with values "script", "function", "module", and maybe "function*", "async function", and "async function*". * Debugger.Source should have a .type property with the value "script" or "module". This tells you how to parse `source.text`. * Debugger.Environment's .type property should identify module scopes; that's part of bug 1414683. * (less important) Debugger.Object should identify module reflector objects and provide a way to get the module Environment.
Nobody has asked for these yet, but there should probably also be: * a way to query a global's table of modules; * when paused in a module, a way to answer the question "why did we load this module in the first place?" The answer might be "it's a <script type=module>" or "X other module imported it". (See also: async stacks.)
You need to log in before you can comment on or make changes to this bug.