tailwindcss 2.0 requires postcss 8 and tailwind-rn is using postcss 7
See original GitHub issueeverytime I try to use npx creaate-tailwind-rn
I get this error:
/node_modules/tailwind-rn/node_modules/postcss/lib/processor.js:153
throw new Error('PostCSS plugin ' + plugin.postcssPlugin + ' requires PostCSS 8.\n' + 'Migration guide for end-users:\n' + 'https://github.com/postcss/postcss/wiki/PostCSS-8-for-end-users');
^
Error: PostCSS plugin tailwindcss requires PostCSS 8.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:6
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Error: PostCSS plugin tailwindcss requires PostCSS 8
As of v2.0, Tailwind CSS depends on PostCSS 8. The previously accepted answer states how to downgrade to PostCSS 8.
Read more >PostCSS plugin tailwindcss requires PostCSS 8. #2854 - GitHub
Solve it with the below. https://tailwindcss.com/docs/installation#post-css-7-compatibility-build. npm uninstall tailwindcss postcss ...
Read more >Install Tailwind CSS using PostCSS
Installing Tailwind CSS as a PostCSS plugin is the most seamless way to integrate it with build tools like webpack, Rollup, Vite, and...
Read more >How to fix "PostCSS plugin tailwindcss requires PostCSS 8"
I just upgraded to Tailwind 2.0 from Tailwind 1.0, and got the error “PostCSS plugin tailwindcss requires PostCSS 8” when I tried to...
Read more >postcss-import 13 & tailwindcss 2 - Laracasts
I have a repository with Laravel 8 and Tailwind CSS v2, one with the backward compatible version for PostCSS 7 and one for...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@aswinmohanme is right, it’s no longer an issue in
3.0.0
.This has been fixed in the new
tailwind-rn
version