Skip to content
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

Support Tailwind CSS 3 #51

Closed
diamondobama opened this issue Dec 10, 2021 · 3 comments
Closed

Support Tailwind CSS 3 #51

diamondobama opened this issue Dec 10, 2021 · 3 comments

Comments

@diamondobama
Copy link

Tailwind CSS 3 was officially released yesterday but I couldn't install it on Nuxt because of below:

"peerDependencies": {
  "tailwindcss": "1 || 2 || 2.0.1-compat"
},

When should we expect an update for TCV to support version 3 of Tailwind?

@rogden
Copy link
Owner

rogden commented Dec 10, 2021

Thanks for the issue. I'll issue a fix this weekend. In the meantime you can disable the tailwind viewer in Nuxt and run: npx tailwind-config-viewer in the directory that contains your tailwind.config.js file.

@michaelpumo
Copy link

I also get this issue. I need to run npm i --force in order to get dependencies installed (not ideal!).

Once I do though, config viewer appears to work fine with Tailwind 3...so I guess it's just because of config/dependency settings in this package.

➜  prosperly git:(main) ✗ npm i
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: prosperly@1.0.0
npm ERR! Found: tailwindcss@3.0.7
npm ERR! node_modules/tailwindcss
npm ERR!   dev tailwindcss@"^3.0.7" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer tailwindcss@"1 || 2 || 2.0.1-compat" from tailwind-config-viewer@1.6.2
npm ERR! node_modules/tailwind-config-viewer
npm ERR!   dev tailwind-config-viewer@"^1.6.2" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

@rogden
Copy link
Owner

rogden commented Dec 20, 2021

Fixed in 1.6.3

@rogden rogden closed this as completed Dec 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants