fix: Add support for rollup 3

[mathiasschopmans]

Fixes #224

[hanorine]

Would love to get this support merged in as soon as possible. Thanks.

[mryechkin]

@Anidetrix any chance of this getting looked at? My team has just recently updated to Rollup v3 and are looking to start using this plugin, but are blocked due to the v2 limitation.

Locally I can still install with -f flag, but that won't work for deployment pipelines.

Thank you

[drzraf]

Quoting https://github.com/Anidetrix/rollup-plugin-styles#why

Because alternatives did not look good enough - they are either too basic, too buggy or poorly maintained.

:|

[mryechkin]

FYI - I've moved on to using the @ironkinoko/rollup-plugin-styles package, which looks to be a v3 compatible fork.

[hanorine]

FYI - I've moved on to using the @ironkinoko/rollup-plugin-styles package, which looks to be a v3 compatible fork.

That worked for me. I hope his changes will be merged into here.

[julianjelfs]

Also - add support for rollup 4 😂 - please please

[megheaiulian]

I have created a fork at https://github.com/plumelo/rollup-styles rollup-styles that supports rollup v3 and v4.

[RoryDuncan]

I have created a fork at https://github.com/plumelo/rollup-styles rollup-styles that supports rollup v3 and v4.

For your potential future packages, @megheaiulian—rollup plugins are supposed to follow the naming convention "rollup-plugin-<package>". Bit late now—just letting you know the convention exists.

[megheaiulian]

@RoryDuncan I am aware of that convention but i couldn't find any good and meaningful unprefixed npm package name.
If you have a good suggestion I'd welcome it. The package can be renamed while having previous names and versions still working ...

Renamed the fork to rollup-plugin-styler.