Elpy VS estree

If you want to stick with Elpy, I'd suggest side-stepping the RealPython tutorial and diving in to Elpy's documentation directly. But keep in mind that the project has been looking for a new maintainer since March of 2021.

Elpy allows to do that with its folding module.

you can use elpy for that its not lsp but it might be faster than pyright.

The last commit in https://github.com/jorgenschaefer/elpy master was 16 days ago, so it seems yes.

And I'm using Elpy on Emacs. It works like a charm, which provides (quote from it README): - Code completion - Code Navigation - Interactive evaluation and interactive Python shell - On-the-fly syntax checking - Access to documentation

This is one of the (minor) reasons I abandoned anaconda-mode (default for Doom) for elpy. You can do the same with this snippet in your packages.el lisp (package! anaconda-mode :ignore t) (package! elpy :recipe (:host github :repo "jorgenschaefer/elpy") :pin "2203597") ;; Commit date 2021/3/28 Anaconda is lightweight by comparison. Elpy is also a python package that needs to be installed. Read their docs before using. https://github.com/jorgenschaefer/elpy

I (current maintainer of Elpy) am not able to properly maintain the project anymore.

For python development, I use https://github.com/jorgenschaefer/elpy (Elpy is an Emacs package to bring powerful Python editing to Emacs. It combines and configures a number of other packages, both written in Emacs Lisp as well as Python.)

ESLint's AST format, ESTree, would represent this line of code as:

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

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!

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).

ESTree compatible output, AST explorer on WASM

The parser we wrote transforms the GraphQL AST into ESTree structure, so it allows you to travel the GraphQL AST tree easily.

For espree parser(the one eslint uses) we can refer here Eslint AST Node Types