Replies: 2 comments 2 replies
-
We don’t support async parser APIs and we don’t have any plans to do so. The low-level Linter class assumes synchronous parsing, so that would have to be rewritten in order to enable this. I’m not saying we wouldn’t ever do that but we don’t have it on the roadmap. |
Beta Was this translation helpful? Give feedback.
0 replies
-
It seems to be at least among the ideas 😍 |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi, I'm author of the swc project. https://swc.rs/
The swc proejct has a fast javascript / typescript parser written in rust. It's a native module and as a result it can use the thread pool of libuv.
If eslint supports asynchronous parser api, we can offload parsing to backgorund threads. Parsing will not block the js thread, which is busy processing eslint rules. So performance will be greatly improved.
I'm asking this because https://eslint.org/docs/developer-guide/working-with-custom-parsers#working-with-custom-parsers does not mention asychronous parser apis.
Beta Was this translation helpful? Give feedback.
All reactions