astexplorer
A web tool to explore the ASTs generated by various parsers. (by fkling)
vscode-language-tree
VSCode tree format support (by nin-jin)
Our great sponsors
astexplorer | vscode-language-tree | |
---|---|---|
43 | 2 | |
5,942 | 5 | |
- | - | |
6.0 | 4.3 | |
3 days ago | about 1 year ago | |
JavaScript | TypeScript | |
MIT License | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
astexplorer
Posts with mentions or reviews of astexplorer.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-04-06.
-
Understanding Code Structure: A Beginner's Guide to Tree-sitter
You can play with your code here, and visualise ASTs for the same.
-
What is an Abstract Syntax Tree in Programming?
Website
-
How to create your own Eslint rule with tests, boosting the DX, and code-review
To understand this syntax, I recommend exploring AST Explorer. You will have a better view of how the AST of JavaScript works and how to correlate it with the Eslint syntaxy:
-
Programming from Top to Bottom - Parsing
You can never mistake type_declaration with an identifier, otherwise the program will not work. Aside from that constraint, you are free to name them whatever you like, there is no one standard, and each parser has it own naming conventions, unless you are planning to use something like LLVM. If you are interested, you can see examples of naming in different language parsers in the AST Explorer.
-
ESLint: under the hood
The rule that I want to write will be called not-allows-underscore: the idea is to abolish the use of underscores when declaring variables or functions. It's a real dummy rule, but it should be enough to see in action the concepts that we have discussed earlier. The first thing that I would do is to go to AST Explorer, write down a code that declares variables and functions (both standard and arrows one) and take a look at what type of node is the one that encodes the identifier. Doing that, I found out that the node type of my interest is Identifier, what a surprise! 🤣. In particular, the structure of the node holds the string used as identifier in the name property.
-
😱 ESlint over Conventions - You have Not unlocked the power of ESlint 😱
All the information about the API, AST node names, AST Explorer, etc. you can read in the official documentation. I’m just going to show examples of how to automate the check-up of our created conventions.
- AST Exploret
-
200 Web-Based, Must-Try Web Design and Development Tools
AST Viewer
-
Building a JSON Parser from scratch with JS 🤯
If you want to see how the AST of popular languages looks, I recommend the AST Explorer. It supports various languages, and you can view the complete AST and navigate through the nodes. If you want to go further, you can try to copy some logic from an existing parser and implement it in your own, such as calculating an expression according to precedence order, for example: 1 + 2 * 3 (which is 7, not 9).
-
Creating my own typescript compiler
https://astexplorer.net/ is a good resource/playground for understanding ASTs and transpilers.
vscode-language-tree
Posts with mentions or reviews of vscode-language-tree.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-02-17.
-
What is wrong with SOURCE MAPS and how not to mess with them?
I have a wild idea - for each IDE, make one universal plugin that can read the declarative description of the language syntax and use it to provide basic integration with the IDE: highlighting, hints, validation. I have so far implemented highlighting.
-
Tree - AST which kills JSON, XML, YAML, TOML, etc
VSCode
What are some alternatives?
When comparing astexplorer and vscode-language-tree you can also consider the following projects:
deno_swc - The SWC compiler for Deno.
tree.d - Tree - simple fast compact user-readable binary-safe extensible structural format
gogocode - GoGoCode is a transformer for JavaScript/Typescript/HTML based on AST but providing a more intuitive API.
HabHub - Peering social blog
ChakraCore - ChakraCore is an open source Javascript engine with a C API.
mam_mol - $mol - fastest reactive micro-modular compact flexible lazy ui web framework.
Acorn - A small, fast, JavaScript-based JavaScript parser
atom-language-tree - Tree format support in Atom
proposal-type-annotations - ECMAScript proposal for type syntax that is erased - Stage 1
slides - Мои слайды для конференций
Smol-sublime - Sublime syntax-highlighting for *.view.tree of $mol
astexplorer vs deno_swc
vscode-language-tree vs tree.d
astexplorer vs gogocode
vscode-language-tree vs HabHub
astexplorer vs ChakraCore
vscode-language-tree vs mam_mol
astexplorer vs Acorn
vscode-language-tree vs atom-language-tree
astexplorer vs proposal-type-annotations
vscode-language-tree vs slides
astexplorer vs tree.d
vscode-language-tree vs Smol-sublime