feat: postcss 8 and new modern postcss API

[anikethsaha]

Adding support for new postcss 8 and its new API

Status

• dep updates
• test helpers
• site playground
• cssnano core
• postcss-colormin
• postcss-convert-values
• postcss-discard-comments
• postcss-discard-empty
• postcss-discard-duplicates
• postcss-discard-overridden (the test runner needs to be fixed)
• postcss-discard-unused
• postcss-merge-idents
• postcss-merge-longhand
• postcss-merge-rules
  • plugin refactor
  • tests case for should not crash when node.raws.value is null not working properly as postcss runner is not able to run the plugin - maybe the postcss is < 8 there, not sure. error 'true' is not a postcss plugin when using the postcss-simple-vars plugin
• postcss-minify-font-values
• postcss-minify-gradients
• postcss-minify-params
• postcss-minify-selectors
  • the plugin code
  • tests: the toModules plugin's visitor keys are not being visited. But the plugin is being called. Need to fix that.
  • (non-blocker): Support for postcss 8 ? csstools/postcss-font-magician#91
• postcss-normalize-charset
• postcss-normalize-display-values
• postcss-normalize-positions
• postcss-normalize-repeat-style
• postcss-normalize-string
• postcss-normalize-timing-functions
• postcss-normalize-unicode
• postcss-normalize-url
• postcss-normalize-whitespace
• postcss-ordered-values
• postcss-reduced-idents
• postcss-reduced-initial
• postcss-reduced-transform
• postcss-svgo
• postcss-unique-selectors
• postcss-zindex
• stylehacks
• postcss-calc (external)
  • it is supported in upstream
  • need to update dependency in our end
• css-declaration-sorter (external)
  • it is supported in upstream postcss 8 support ? Siilwyn/css-declaration-sorter#106
  • need to update dependency in our end
• autoprefixer (external)
  • it is supported in upstream
  • need to update dependency in our end

[alexander-akait]

Can you separate PRs, one plugin = one PR, PostCSS 8 should have compatibility with existing plugins, so we will have only warnings, if you faced with a error, need report to postcss repo

[anikethsaha]

I guess there would be some issues as we have our own runner. here

here is the diff

So I guess it is better to do this in a single one itself. We do have nightly as well and implementing some support for postcss 8 and rest in postcss 7 might break.

[ludofischer]

Hi, would you find it useful if I converted some of the remaining plugins myself? I could open a pull request against your postcss-8 branch.

[anikethsaha]

Hi, would you find it useful if I converted some of the remaining plugins myself? I could open a pull request against your postcss-8 branch.

Sounds good. @evilebottnawi do we have to wait for the postcss fixes you were working on to continue in this?

[alexander-akait]

@anikethsaha I think all problems fixes in 8.1, so we can continue to update

[ludofischer]

Shall I start from postcss-normalize-charset and go down the checkbox list?

[anikethsaha]

Shall I start from postcss-normalize-charset and go down the checkbox list?

Sure,
I would recommend not to update the integration test's fixtures. We will do that once everything is migrated. You can update rhe plugin's tests.

[ludofischer]

All right. BTW, when I run yarn test:only on the postcss-8 branch, Jest hangs. It prints the test results summary so it does manages to run all the tests anyway.

[alexander-akait]

Done in master

[frederikhors]

Please can you release it? The world is waiting for you.

[alexander-akait]

It would be nice if the world helped me and not wait... we always glad to see new contributors

[frederikhors]

Believe me, I would love to know where to start to help you. Geniuses like you often underestimate themselves.

[ludofischer]

I would gladly help tag and publish a release candidate, but I haven't got the permissions though. Don't know if there are changes that still need to be merged.