Add: Interactive AST Visualizer & Parser Studio - #803
Merged
praveenscience merged 1 commit intoJul 30, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Closes #791
Adds Interactive AST Visualizer & Parser Studio (
tools/ast-visualizer-studio.html) under theDeveloper Utilitiescategory. The tool provides a real-time syntax tree tokenizer and parser to inspect and visualize JavaScript and JSON source code as structured Abstract Syntax Trees (ASTs) with expandable node trees, scope symbol inspectors, and JSON export capabilities.Type of Change
Screenshot
Checklist
add/tool-name,feat/description, orfix/description)For new tools:
.htmlfile in thetools/folderast-visualizer-studio.html)data/tools.jsonwith all required fieldstools/ast-visualizer-studio.pngnext to the HTML filenode scripts/sort-norm.js data/tools.jsonto sort and normalize the tools registrynode scripts/build.jsand verified the landing page renders correctly