Skip to content

VSCode Tailwind Extension? #109

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

Closed
sprite2005 opened this issue Dec 22, 2021 · 6 comments
Closed

VSCode Tailwind Extension? #109

sprite2005 opened this issue Dec 22, 2021 · 6 comments

Comments

@sprite2005
Copy link

Does anyone know how to get this working in Rails 7 with the Tailwind CSS VS Code extension?

[Error - 9:25:27 AM] Tailwind CSS: Can't resolve 'tailwindcss'

@alex-damian-negru
Copy link

alex-damian-negru commented Dec 26, 2021

From what I noticed the VSCode extension looks for the tailwind.config.js under root namespace, while this gem expects it under config.

Although not a viable solution, it might work if you duplicate the file to have it in both namespaces. I haven't found an option to provide the namespace where either this gem or the VSC extension should look for the file.

@stephenbiggs
Copy link

I've also been struggling to get this to work. The above suggestion didn't seem to resolve the issue. Look forward to potential solutions.

@richjdsmith
Copy link

There is a related thread that discusses this issue for other rails users. may also have to do with TailwindCSS 3.

tailwindlabs/tailwindcss-intellisense#448

@Admiral-Enigma
Copy link

I get the same error
[Error - 19.52.33] Tailwind CSS: Can't resolve 'tailwindcss' in 'c:\Users\User\Desktop\railsproject\config'
So it's looking in the right folder but I think it may be related to the fact that the tailwindcss node package is missing as a dev dependency.

@onurozer
Copy link

onurozer commented Jan 5, 2022

I have the same error. It looks like Tailwind Extension does not work with the CLI version of Tailwind.

@bpo
Copy link

bpo commented Jan 9, 2022

Release v0.7.5, from 2 days ago, ships with its own copy of the node package - that resolves this issue for me.

@dhh dhh closed this as completed Jan 16, 2022
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

8 participants