Merge Stylecow and PostCSS
ai opened this issue · comments
I think that your project always has better API. It is more clear. And “event based” API solves many “postprocessor” problems.
But on the other hand PostCSS has better parser and ecosystem (because of Autoprefixer).
But this difference is not because of different goals or different architecture. For example, PostCSS community is planning to implement same “event based” API.
Maybe we should join project to make better product for users? Because we spend our time in different projects and user has no best solution (for example, with best barser, plugins ecosystem and API).
There are great examples when community was united to became better for users: io.js and node.js, 6to5 nd esnext, Merb and Rails.
We want to start 5.0 branch in the end of summer, so we can broke PostCSS API with your awesome ideas.
What do you think about it?
Hi. I think it's a good idea.
Stylecow was created 4 years ago as an internal tool to ease the work with pure css, when there wasn't any similar tool available (less and sass use its own syntax). The library was improved and ported to javascript (originally it was written in php) but never got much popularity.
When we discovered postcss, we gave it a chance. It has a similar goal but with a big ecosystem and comunity behind, but I didn't suit our needs. We needed a tool to work with css, not only to install plugins and postcss is hard to develop with it and it has many plugin conflicts, so we keep using stylecow.
I'm happy to know you want to change postcss to be more similar to stylecow, so, in this case there are benefits for both parts. In the point of view of the architecture, this is a big change, because stylecow is based in an advanced and heavy core (parser, coder, api, etc) with small plugins meanwhile postcss has a light and fast parser with complex plugins.
Anyway, if we can get the best of both parts, it was fantastic.
👍 I'd be interested in helping with this
intriguing. I certainly like the idea of creating the best of both worlds. Has any progress been made? In the interim, are there any tutorials or videos available on working with Stylecow? I'm curious about integration with existing task runners / build tools. Thanks.
Hi, @RobertVisser I think the merge is shelved.
If you're interested, you can read about the stylecow usage here and here about the core and API.
And about the integration, there are plugins for grunt, gulp, webpack and jsTransformer
So, how this matter is going ? Has been there any progress ?
I think this will never happen. I've stopped developing stylecow 3 years ago.
If anyone is interested in continuing the project, I'm open to transfer it.
Hello there, I am a beginner programmer. I know javascript, typescript and little bit of rust I use Deno for my projects but in past i have worked with Node.
I love to create my own stuff from scratch and that's why I am trying to understand postcss so that I could re-write from scratch and learn how pre-processors work.
I would love to continue this project.