Library maintenance

[ream88]

Hey to all users of my library!

You may have noticed that I'm currently struggling to keep it updated. There are several reasons for this, but the primary one is that I have stopped using it entirely. Consequently, I am exploring a couple of potential solutions:

• Transfer the library to someone on npmjs.com, who is prepared to take on the responsibility of maintaining it.
• Automate the versioning process so that every time a new version of any dependency is released, the library automatically builds and releases a new version.

Your thoughts and feedback on these ideas would be greatly appreciated. Thank you for your understanding and support!

[schuer]

I can’t support, unfortunately. Just want to say thank you for your work so far! 🙌

[Quentame]

Hi there !

Sorry to bother you, but it seems you released an v10.0.0 (on commit 79d1d66) but not push it to npm (https://www.npmjs.com/package/stylelint-config-idiomatic-order).

Could you do it ?

Details here #85

Thanks for all your work ❤️

[mutoe]

May I ask what's your new choose after you stopped using it? :)

[ream88]

May I ask what's your new choose after you stopped using it? 😊

When I do some frontend work these days, it's usually done with Tailwind. I really like the approach of having structure and styles in the same source code, and actually came up with something similar (but by far not so polished) for our apps before Tailwind was even released. 😉

[mutoe]

When I do some frontend work these days, it's usually done with Tailwind. I really like the approach of having structure and styles in the same source code, and actually came up with something similar (but by far not so polished) for our apps before Tailwind was even released. 😉

Oh, I see. Tailwind style, it's more convenient, but I feel like it's more like inline style in elements, but I prefer a standalone css file, which will make me focus more on the business logic than the style.

Of course, every project is different, and there is no one style that is the best, only the more suitable. Thank you for sharing~ 😄

[julienw]

I hadn't seen this issue before, but I'd be happy to help with the support as we're using it in our project, and I don't see that this will change in the near future.

(I also happen to have one PR open ready to be merged :-D)