Open
Bug 1436580
Opened 7 years ago
Updated 2 years ago
Debugger: Module support
Categories
(Core :: JavaScript Engine, enhancement, P3)
Core
JavaScript Engine
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox60 | --- | fix-optional |
People
(Reporter: jorendorff, Unassigned)
References
(Blocks 2 open bugs)
Details
* 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.
Reporter | ||
Updated•7 years ago
|
status-firefox60:
--- → fix-optional
Priority: -- → P3
Reporter | ||
Comment 1•7 years ago
|
||
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.)
Updated•7 years ago
|
Blocks: harmony:modules
Updated•6 years ago
|
Blocks: js-devtools
Updated•4 years ago
|
Blocks: js-debugger
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•