Outdated PostCSS

[romainmenke]

Describe the Bug

PostCSS is listed as a direct dependency with a pinned version.
This makes it impossible for users to use plugins that require a higher version.

Context : csstools/postcss-plugins#147

Expected

PostCSS should be peer dependency with relaxed constraints

having a slightly more flexible issue template would also be nice :D

[romainmenke]

@balazsorban44 #33142

This does fix the immediate bug people might be having, but doesn't fix the underlying issue.

Those versions should not be pinned and postcss should be a peer depedency.
Only a matter of time before this happen again.

[romainmenke]

Tailwind is a good example of how to handle this : https://github.com/tailwindlabs/tailwindcss/blob/62569092e7ba79fc45f77451c179b3f6cc0f80f8/package.json#L62-L65

[romainmenke]

@timneutkens @ijjk @balazsorban44 please keep in mind that you will need to do this regularly and that you can also expect bug reports with the inverse.

It is also possible for plugins to only work with older versions of PostCSS.
This should be rarer with semver, but it still happens.

Maybe better to consider a more sustainable solution that gives some freedom to users?

[balazsorban44]

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.