TL;DR: Native parsers used in JavaScript are not always faster due to extra work across languages. Avoiding these overhead and using multi-core ar...
For further actions, you may consider blocking this person and/or reporting abuse
A few weeks ago, I tried ast-grep, but I ended up deleting it because I didn't think it could replace eslint.
Does ast-grep support linting for complex use cases?
Eslint's rules are based on JavaScript, so I was able to create rules that support auto-fixes for even extreme cases.
ast-grep CLI is designed to support quick rule creation and ad-hoc code refactoring. It is not designed to replace eslint, indeed. However, you can create complex rule by using the @ast-grep/napi JS API!
I am not sure how complex use cases you are mentioning. But ast-grep.github.io/catalog/ this page has a curated list of ast-grep rules. :)
A great article! It’s nice to see #Rustlang being used in more and more places.
Check out BABLR! It's a developing alternative to tree-sitter designed to be a natural successor to Babel. No FFI or serde costs and it not only keeps ESLint's power and extensibility but combines it with Babel's. github.com/bablr-lang
It'll probably be another month or two before I have a working Typescript grammar and a stable version of the VM though.