this is important if we want to use ast instead of cst

大佬有做与postcss(js)的测试对比吗

Though we have a relative stable parser, but still have some corner case that we don't handle, maybe it's better to have a playground help for displaying some issue.

Weekly Downloads > 10M

• #82
• #86
  • postcss-selector-parser
  • postcss-value-parser
• #85
• #84
  • postcss-selector-parser
• #83
• cssnano
• #94
• #99

Hi, I thought about a rust implementation of postCSS for quite some time and I'm glad this attempt exists.
I am a beginner in Rust and while I was able to put together a basic parser using nom, I recon when it comes to visiting and changing the AST I do lack lot of experience with some Rust idiomatic patterns and especially memory management...

I still would like to learn more of the language and I see this project is definitely one I'd like to keep an eye on and eventually contribute to, I do maintain a CSS framework based on postcss-modules and on the long term I'd love to migrate it to rust to make it faster.

I opened this ticket to try and get an overview of the status of the project and how to best contribute.

1. Is the project currently actively developed? Is there a tentative roadmap or list of known issues/tasks beside the missing plugins?
2. Would be great to have a contributing guide, a basic description of the architecture and especially a guide to write plugins that may be the most approachable area for external contributors
3. I am also curious about the plugin API in general, in my mind I envisioned both a Rust API with some Plugin trait with a stable API, as well as maybe a way to use WASM compiled plugins as that may open the door to a larger community and possibly better integration with JS based pipelines (even though most likely lower speed). I wonder if this is something that was discussed and what are your thoughts about it

https://github.com/css-modules/icss-utils/blob/master/src/createICSSRules.js

This project is very good.I want to use it in JS now, there is corresponding npm？