Conversation
|
I've published a fork in the meantime: https://www.npmjs.com/package/@pioug/rollup-plugin-css-only. It should be almost like a drop-in replacement. "rollup-plugin-css-only": "npm:@pioug/rollup-plugin-css-only@^5.0.0",For reference, the equivalent changes for rollup-plugin-import-css (jleeson/rollup-plugin-import-css#18) have been merged too. @thgh, I can help maintain this plugin, at least by handling the chores, if you accept. I use it at work, so I don't mind spending time on it. |
|
Hi @pioug what can I do to help you maintain this plugin? I have invited you to the repo, feel free to resolve/merge where needed. Consider keeping changes small (or add tests). Also consider if this plugin could be moved to the @rollup/plugins repo. |
|
Published in v4.4 |
|
Thank you so much, @thgh, for the invitation 🙏 I think one thing that may be helpful too is having publishing rights on npm (my account: https://www.npmjs.com/~pioug) 💦 Like here, for example, I think the v4.4 is not published yet?
That sounds even better and sustainable! |
|
Oops, it errored, published for real now! https://www.npmjs.com/package/rollup-plugin-css-only I'm ok transfering publishing rights, but security wise I would like to wait for a while and build some trust first. (most people volunteering to maintain and getting repo access end up not maintaining after all, so would rather limit the blast radius) |
Tests seem to be passing, and I'm not seeing anything immediately relevant in the release notes.