Structured-Commenting
estree
Structured-Commenting | estree | |
---|---|---|
2 | 8 | |
0 | 4,970 | |
- | 0.7% | |
0.0 | 5.3 | |
almost 2 years ago | 7 months ago | |
- | GNU General Public License v3.0 or later |
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.
Structured-Commenting
-
Can cargo fmt preserve whitespace depth?
I recognize not many others currently do it but it has allowed me to explicitly state which lines a comment is talking about. All while not being any more verbose and be able to nest multi-line comments, which I have personally found invaluable for increasing code clarity and readability. For that reason I have made a repo explaining how to use it if others decide they find it useful.
-
Representing and printing hierarchies
I am playing around with writing a program that will give a hierarchical description of source code written with my Structured Commenting scheme. So for now I would just like a hierarchical data-structure that I can create and visualize.
estree
-
ESLint Understand By Doing Part 1: Abstract Syntax Trees
ESLint's AST format, ESTree, would represent this line of code as:
-
Eglot has landed on master: Emacs now has a built-in LSP client
That was a super interesting link, thank you.
For the ontological problem, I presume you're referring to how there are so many differing ideas of how to represent ASTs (apologies for mixing languages, these URLs were just handy):
* https://lisperator.net/uglifyjs/ast#nodes
* https://github.com/estree/estree#the-estree-spec
* ... likely others
which makes it hard for ls1 to ask ls2 about "the for-of iteration variable Node" because ls2 could be using UglifyJS or ESTree or their own(!) AST nomenclature?
And all of this is made worse by (e.g.) Java1.3 versus Java19 because languages are rarely static
-
Statements vs. Expressions
I find it better to actually look at the AST for javascript.
These are expressions:
https://github.com/estree/estree/blob/master/es5.md#expressi...
These are statements:
https://github.com/estree/estree/blob/master/es5.md#statemen...
I guess the confusing part for many is how an expression can also be a statement. But if you look at the ExpressionStatement you see that an expression is not also a statement. It's just the wrapper statement!
-
A technical tale of NodeSecure - Chapter 2
When I started the NodeSecure project I had almost no experience 🐤 with AST (Abstract Syntax Tree). My first time was on the SlimIO project to generate codes dynamically with the astring package (and I had also looked at the ESTree specification).
- Show HN: Monocle – bidirectional code generation library
-
Go is the future of Frontend infrastructure
ESTree compatible output, AST explorer on WASM
-
Introducing GraphQL-ESLint!
The parser we wrote transforms the GraphQL AST into ESTree structure, so it allows you to travel the GraphQL AST tree easily.
-
Revealing the magic of AST by writing babel plugins
For espree parser(the one eslint uses) we can refer here Eslint AST Node Types
What are some alternatives?
proposals - Tracking ECMAScript Proposals
esprima - ECMAScript parsing infrastructure for multipurpose analysis
design - Ewasm Design Overview and Specification
babel-parser
escodegen - ECMAScript code generator
kataw - An 100% spec compliant ES2022 JavaScript toolchain
Acorn - A small, fast, JavaScript-based JavaScript parser
babel-handbook - :blue_book: A guided handbook on how to use Babel and how to create plugins for Babel.
qwik - Instant-loading web apps, without effort
graphql-eslint - ESLint parser, plugin and set rules for GraphQL (for schema and operations). Easily customizable with custom rules. Integrates with IDEs and modern GraphQL tools.
cli - JavaScript security CLI that allow you to deeply analyze the dependency tree of a given package or local Node.js project.