-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Choosing the parsing backend #9
Comments
I found a benchmark between chumsky and nom: zesterer/chumsky#94 |
Chumsky seems well maintained and apparently very fast. I'm leaning towards it. |
From looking into Svelte Parser HTML is parsed using its own parser while javascript an CSS are both parsed by 3rd party libraries. Rustle could use a similar approach by parsing javascript with swc_ecma_parser or another parser and CSS with another library. |
Yeah after looking into it, I think I'm going to use the swc crates for parsing the js and css and try and rewrite their html compiler |
Does swc have a css parser? |
I looked around in the swc crates and I found it |
Some options are:
nom
andpest
seem to be the most popular right now.Any other suggestions? Tell me what we should use
The text was updated successfully, but these errors were encountered: