You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've started using CSS Modules and suddenly, the only reason to keep using Sass is that I love Susy and I don't want to stop using it.
I'm already using PostCSS for doing things (like autoprefix), so in the quest for simplicity, it would be great for my front-end stack to be able to include Susy as a PostCSS plugin, and wish a safe trip to the old and good Sass.
I'm interested into porting threeishto PostCSS, but I don't know what would be the preferred way to do that. Should I just fork this repo and start doing it on my own? Maybe send a PR to this repo once it's done?
The text was updated successfully, but these errors were encountered:
Hi @mbavio — I don't think we'll pull a postCSS port into this repo — but you are welcome to fork and work on it yourself. If you get something working, I'll be happy to mention it on the website, and point people in your direction!
I've started using CSS Modules and suddenly, the only reason to keep using Sass is that I love Susy and I don't want to stop using it.
I'm already using PostCSS for doing things (like autoprefix), so in the quest for simplicity, it would be great for my front-end stack to be able to include Susy as a PostCSS plugin, and wish a safe trip to the old and good Sass.
I'm interested into porting
threeish
to PostCSS, but I don't know what would be the preferred way to do that. Should I just fork this repo and start doing it on my own? Maybe send a PR to this repo once it's done?The text was updated successfully, but these errors were encountered: