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