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

[Bug] Missing resolver #2511

Closed
1 task
JesusTheHun opened this issue Feb 24, 2021 · 3 comments
Closed
1 task

[Bug] Missing resolver #2511

JesusTheHun opened this issue Feb 24, 2021 · 3 comments
Labels
bug Something isn't working

Comments

@JesusTheHun
Copy link

  • I'd be willing to implement a fix

Describe the bug

While trying to install the very popular tailwindcss, I run into this error :

$ yarn add -D tailwindcss@npm:@tailwindcss/postcss7-compat @tailwindcss/postcss7-compat postcss@^7 autoprefixer@^9
➤ YN0001: │ Error: tailwindcss@npm:@tailwindcss/postcss7-compat isn't supported by any available resolver
...

To Reproduce

The commend above will trigger the error. I tried to run this into Sherlock but it seems broken itself :/

Environment if relevant (please complete the following information):

  • OS: OSX 11.2.1
  • Node version: 15.8.0
  • Yarn version: 2.4.0
@JesusTheHun JesusTheHun added the bug Something isn't working label Feb 24, 2021
@merceyz
Copy link
Member

merceyz commented Feb 24, 2021

tailwindcss@npm:@tailwindcss/postcss7-compat

You're lacking a version, try

yarn add -D "tailwindcss@npm:@tailwindcss/postcss7-compat@*" @tailwindcss/postcss7-compat postcss@^7 autoprefixer@^9

Duplicate of #1816

@merceyz merceyz closed this as completed Feb 24, 2021
@JesusTheHun
Copy link
Author

JesusTheHun commented Feb 24, 2021

Don't you think you should support that format as a compatibility feature ? Since the package manager next door support this syntax.

Edit : one should also note that the issue has been reported to tailwindcss and their response is pretty clear :

This sounds like a Yarn 2 or system related issue to me unfortunately, as this works as expected with npm. Going to close as no plans to dig in to this ourselves and this is the first time it has been reported. If it's a widespread issue we can circle back, or hopefully someone who actually uses Yarn 2 and has run into it and fixed it can share their solution.

@merceyz
Copy link
Member

merceyz commented Feb 24, 2021

Don't you think you should support that format as a compatibility feature ?

Sure, the issue this is a duplicate of is still open for that reason

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants