-
Notifications
You must be signed in to change notification settings - Fork 280
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide a diagnostic tool #260
Comments
Yes please, this would make debugging these issues much easier |
Could even pop open the browser and/or write an HTML file with details. We have a lot of data and being able to display it in a richer form than the debug console may make life easier. The analyzer could be built into it as well. That alone would make my debug loop a little faster. |
Sort of related, I have imagined a workflow where you can click a source that looks like |
Added a new command
|
I get the following error when running this new
Is this a bug or am I missing something? |
Thanks for pointing that out; fixed in the next nightly |
I can confirm it works in |
Where is this now? I've been following a trail of issues from the original .scripts command to this issue, but I can't find any |
The command seems to have been renamed to |
In the next release I added a simple rewrite so |
The v1 adapter has the
.scripts
command which dumps info about which scripts are loaded, the sourcemap info, and how the paths are finally resolved after applying overrides. It would be useful to have the same in this adapter. Would be awesome to have this in GUI form, a custom treeview, or opening an editor with a nicely formatted markdown grid, or something more user friendly than what v1 does.The text was updated successfully, but these errors were encountered: