-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compatibility with PostCSS 8 #52
Comments
@jonathantneal Do you have any plans to support PostCSS 8 in Looking at the installation instructions for Tailwind with create-react-app paints a good picture how this has far reaching consequences: https://tailwindcss.com/docs/guides/create-react-app All I'm asking is a heads up if this is not going to happen or if there's help wanted. Thanks for all your hard work for the community so far! |
Time. It’s all just a matter of time. I take runs at completing this, but rarely have enough time to get them across to publish |
Cheers Jonathan for the update! In other words, if there are people in the community reading this with a good understanding of the libraries and can perhaps even contribute on company time, then PRs would be welcomed? |
Yes, so very welcomed. |
@jonathantneal what progress have you made those far? have any commits yet? |
True, i really want to get this up and going but not sure if i did this right for this plugin |
This has been resolved in https://github.com/csstools/postcss-normalize/tree/10.0.0 |
You're awesome! @jonathantneal |
Thanks for your PostCSS plugin!
As you probably know, PostCSS 8 was released a few days ago. It would be great if you could make this plugin compatible with the latest version. The creators of the project have even released this migration guide.
The text was updated successfully, but these errors were encountered: