TheLarkInn / js-parser-discussions

Discussions & Collaboration on a Unified/Base set of parser features for JavaScript
42 stars 1 forks source link

Highlight Dependencies #4

Open xjamundx opened 8 years ago

xjamundx commented 8 years ago

Which projects are using which tool?

In my head everyone has pretty much converged around acorn, but maybe babylon will become the new standard. I have a fairly limited set of tools I work with however, so it would be nice to see a list of modern projects and which parsers they use.

eslint for example uses espree, but mostly as a simple translation layer between acorn and esprima for error handling and other things, since eslint originally used esprima and now uses acorn under the hood (via espree).

TheLarkInn commented 8 years ago

A list would be good. I agree.

xjamundx commented 8 years ago

Also of note are download stats for the 4 big esprima-like parsers:

  1. https://www.npmjs.com/package/esprima
  2. https://www.npmjs.com/package/acorn
  3. https://www.npmjs.com/package/babylon
  4. https://www.npmjs.com/package/espree
ariya commented 8 years ago

Download count can be done using shields, here is one for Esprima: npm download.

However, I question the value of displaying it. For the purpose of the discussion, it can be considered as a vanity metric, a popularity contest. The merit of the discussion should be as technical as possible.

TheLarkInn commented 8 years ago

Agreed. I think downloads isn't needed in this case. However finding out what depends on each of them maybe has more relevance.