Is CSScomb.js dead?

@tonyganch

Hello there.

In january 2016 @tonyganch wrote the tweet: https://twitter.com/tonyganch/status/686992436871168000

I’m looking for a new maintainer for CSScomb project. If you’d like to help in any way, please write me to tonyganch+csscomb@gmail.com.

Today I see no activity (commits, answers to issue & PRs, new releases, etc).

I’ve got a couple of questions.

The first one: frontend community still need CSScomb.js?

If so, can CSScomb mantainers tell to us a little bit about their vision of CSScomb role. If not… well, maybe it’s time to close project explicitly? Like JSCS did it.

The second one: should CSScomb be deprecated in favor to stylelint or other tool?

cc @mishanga @tonyganch and all active contributors.

I think PostCSS based solution is better. We have special postcss-sorting. And stylelint with stylefmt can do the same.

So, if we port Sass parser to PostCSS and add some extra plugins, we can make easy migrations for CSSComb users.

@ai

@ai

think PostCSS based solution is better.

No.

For those who don’t use postcss at all it’s not better.
CSScomb have 5+ plugins for editors. What about postcss-sorting editor plugins?

@miripiruni

@miripiruni If just take PostCSS as AST provider, isn't it same solution?

@miripiruni

@miripiruni

PostCSS is not a Sass or any special language. Users don’t “write a PostCSS”. So there is no PostCSS users. PostCSS is just a parser. There are Autoprefixer or Stylint users. But some users even don’t know, that their tool is based on top of PostCSS (CSS Modules or webpack are good example). PostCSS is a AST-tool to write a tools for CSS, that’s all. It is not a language.
We can put custom build of several PostCSS plugins into these CSSComb text editor plugins. So it will be like CSSComb API { PostCSS { postcss-sorting, few other plugins } }

We can put custom build of several PostCSS plugins into these CSSComb text editor plugins. So it will be like CSSComb API{ PostCSS { postcss-sorting, few other plugins } }

Looks like the best way. So in case of postcss popularity it make sense for csssomb to have more participants.

I'm not a maintainer, but I use CSSComb with SublimeText for all my work process, so I don't want it to be deprecated or closed :)

I like the idea of sorting rules, so it will be easier to read the css. And we use it as a linter in our project. Personally I use it as a sublime plugin.

There are some issues and since CSSComb is no longer maintained I'm interested in a modern a solution. In my opinion PostCSS is a modern flexible tool with a large community and solution based on it will be a good direction.

For those who don’t use postcss at all it’s not better.

We can put custom build of several PostCSS plugins into these CSSComb text editor plugins.

Sorry, I am far from PostCSS. This will work without installing it?
I use CSSComb with SublimeText plugin for old projects, which I wrote manually.
I will need to install PostCSS, or everything will work as before?

@sashasushko

@sashasushko PostCSS is just a few JS files. You can compile them to one JS bundle file (by webpack or browserify) and use anywhere — in browser, in Ruby on Rails gem or in text editor plugins.

So this is how we have atom-postcss-sorting or sublime-eslint.

The only question — how to run JS in Sublime plugin. But I think that current CSSComb is written on JS too.

I think merging (or deprecating in favor?) this project into stylefmt would be the most logical thing to do. We don't need competing tools that basically do the same. Also stylelint + stylefmt corresponds really well with ESLint and its autofixing. As for editor plugins — there are already plugins for atom, sublime and vim.

@miripiruni

@miripiruni did you understand that when I said “rewrite to PostCSS” I mean deprecate/merge with Stylelint/Stylefmt (or postcss-sorting, it is a open question), because they both are 100% based on PostCSS.

The only question — how to run JS in Sublime plugin. But I think that current CSSComb is written on JS too.

Actually it is solved using nodejs and simple python wrapper for sublime. So I don't see any problem here.

@ai

@ai 👍

@miripiruni

@miripiruni

CSScomb have 5+ plugins for editors. What about postcss-sorting editor plugins?

postcss-sorting has plugins for Sublime Text, Atom and VS Code.

@lahmatiy

@lahmatiy maybe you want to breathe a new life into one more Yandex's project? :)

@tonyganch

@tonyganch 👍 applause!

@tonyganch

@tonyganch I completely agree, especially about GPE.

But what about current activity? PRs? Commits? Issues? You and @mishanga are only maintainers. And if I understand clearly @mishanga is no longer interested in the project, as well as you. And while you searching a new maintainer the project is losing users.

The purpose of this discussion for me:

Try to make hype and attract attention. CSScomb is interesting project. Maybe somebody would like to maintain it?
Bring maintainers attention to the fact that people go to use the other projects. The project looks dead. I think you cannot just passive searching "new blood" in Twitter. You have to be a maintainer. Review PR, responding to questions, etc. Otherwise it’s not a maintaining.

P.S. Thank you for GPE. But I care about CSScomb too.

We can take sugarss parser and create Sass parser very soon.

@miripiruni

@miripiruni
Actually I've applied for this project's maintainer months ago 😥
Sorry for having been so unresponsive these days, as I was too occupied with my daily work recently.

I've got several bugs fixed during the first month after I got access to this repo. But I've got stuck on some longstanding issues. Since Feb., I barely have any spare time to work on these issues (only small chunks of free time, which does no help with digging into the specifics of the code). That's why this project has been so inactive ever since.

It's my first time to take over such a large open source project and I have definitely underestimated the amount of time it would take, my fault :-(

From next month on I think I'll get a little more free time on open source projects and I'll try my best to get things fixed soon. CSScomb.js will get active maintenance, I promise. But as for a thorough refactor/migration from the ground up, it's a different story. We need more help.

This issue still actual for me and many other developers.

Hi guys,

I will add deprecation notice and instructions/script how to migrate to sass-lint in next two weeks or so.

I'm also looking at ways to release stable 4.0 version without some new features but with the latest parser, so the last version at least does not throw parsing errors which have already been fixed.
That will also allow csscomb to be quietly updated with parser-related fixes only with almost no maintenance time required.
Will update you once I come to some solution.

Maybe migration to Stylelint will be more relevant to users? Stylelint still has no Sass support, but it is much more powerful and popular.

@AleshaOleg

BTW, postcss-sass is in development by @AleshaOleg right now. It will use Dart parser, so it will be very stable.

@ai

@ai, I'm not sure Stylelint will get Sass support in near future, and sass-lint has support for the same preprocessors as csscomb (Less included) since they use the same parser underneath. In this situation I vote more for compatibility than anything.
Plus sass-lint team is ready to add whatever we need to their tool in order to help us migrate users.

But anyway, I believe this is a personal decision for every developer, I will just provide docs and script to migrate the config. If a person wants to use Stylelint, of course he is free to choose whatever suits his project better.

I've released version 4.0, parser is updated to the latest stable version, there is a note about "maintenance mode" on top of the README.
I'll continue with other tasks like issues triage and migration docs (for those who desire) in next weeks.
I'm closing this issue, feel free to reopen it or just continue discussion if you have any questions.

Please archive this repo and add a note that it is abandoned. I shouldn't have to find that out from a closed issue. (Though to be fair it's pretty obvious from the last release/commit dates).

Edit: To be clear, no harsh feelings. I know it's incredibly hard to maintain a project of this size. I just think you should be honest and upfront with potential users that you don't have the time for it.

Navigation Menu

Repository navigation

Is CSScomb.js dead? #461

14 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Is CSScomb.js dead? #461

Description

Activity

ai commented on Apr 26, 2016

miripiruni commented on Apr 26, 2016

Yeti-or commented on Apr 26, 2016

ai commented on Apr 26, 2016

ishaba commented on Apr 26, 2016

tachisis commented on Apr 26, 2016

mightyaleksey commented on Apr 26, 2016

sashasushko commented on Apr 26, 2016

ai commented on Apr 26, 2016

mistadikay commented on Apr 26, 2016

ai commented on Apr 26, 2016

mightyaleksey commented on Apr 26, 2016

miripiruni commented on Apr 26, 2016

hudochenkov commented on Apr 26, 2016

mishanga commented on Apr 26, 2016

14 remaining items

veged commented on Apr 27, 2016

miripiruni commented on Apr 27, 2016

miripiruni commented on Apr 27, 2016

ai commented on Apr 27, 2016

haoqunjiang commented on Apr 27, 2016

miripiruni commented on Jan 27, 2017

tonyganch commented on Jan 31, 2017

ai commented on Jan 31, 2017

ai commented on Jan 31, 2017

tonyganch commented on Jan 31, 2017

tonyganch commented on Feb 16, 2017

vincerubinetti commented on Feb 11, 2022

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions