TheLarkInn
Investigate Uglify
A lot of modern tools use an esprima/estree-compatible parser.
Can we find out how many projects are using uglify and if it should be included in this discussion.
They consider themself a parser though. And I believe implement AST parsing by hand (no deps) for 1?
They do, and it's a cool project but it's not ESTree/Esprima compatible from what I understand. It's kind of it's own thing and not really used by any projects outside of minifiers (let's actually find out).
Yeah I think there is lessons learned from it. Pros, cons. Features, etc. Maybe we can update this issue to "Investigate Uglify". Thoughts?
I believe both Uglify and JSHint both implemented their own parsers to do streaming analysis rather than a separate parse / analyze / transform step.
UglifyJS actually does have separate parsing (http://lisperator.net/uglifyjs/parser) / compression (http://lisperator.net/uglifyjs/compress) stages, and allows writing own transformers (http://lisperator.net/uglifyjs/transform).
