eslint-flymake
estree
eslint-flymake | estree | |
---|---|---|
2 | 8 | |
2 | 4,970 | |
- | 0.7% | |
2.4 | 5.3 | |
about 1 year ago | 7 months ago | |
Emacs Lisp | ||
GNU General Public License v3.0 only | 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.
eslint-flymake
-
Eglot has landed on master: Emacs now has a built-in LSP client
> Why wouldn't you want the lint error to be highlighted right as you type the code?
Why do you think you need to involve an LSP for that?. ESLint, as most linters, can take their input from stdin. That is exactly how the eslint-flymake[0] works. Lint on buffer contents, not file on disk. No JSON RPC involved.
0: https://github.com/emacs-pe/eslint-flymake/
-
List of flymake supported languages
Why would there be a canonical list given the fact that anyone can publish a package outside of Emacs core? Who would be in charge of maintaining it? From what I've seen there isn't many backends for the new API but writing your own is straightforward https://github.com/emacs-pe/eslint-flymake. Which languages/linters do you care about?
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?
emacs-direnv - direnv integration for emacs
esprima - ECMAScript parsing infrastructure for multipurpose analysis
doom-emacs - An Emacs framework for the stubborn martian hacker [Moved to: https://github.com/doomemacs/doomemacs]
babel-parser
eight-ball - interactive Magic 8-Ball function for Emacs
escodegen - ECMAScript code generator
flymake-sqlfluff - flymake plugin for SQL using sqlfluff
kataw - An 100% spec compliant ES2022 JavaScript toolchain
dap-mode - Emacs :heart: Debug Adapter Protocol
Acorn - A small, fast, JavaScript-based JavaScript parser
editorconfig-emacs - EditorConfig plugin for Emacs
babel-handbook - :blue_book: A guided handbook on how to use Babel and how to create plugins for Babel.