Skip to content

The README.md file needs updating for v4. #1228

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
adambirds opened this issue Feb 21, 2025 · 7 comments · Fixed by #1364
Closed

The README.md file needs updating for v4. #1228

adambirds opened this issue Feb 21, 2025 · 7 comments · Fixed by #1364
Assignees

Comments

@adambirds
Copy link

The README.md file eneds updating for v4. Specifically regarding config files.

@philipp-spiess
Copy link
Member

@adambirds Can you clarify? Do you mean the screenshot in the linting section? https://github.com/tailwindlabs/tailwindcss-intellisense?tab=readme-ov-file#linting

@thecrypticace thecrypticace self-assigned this Feb 21, 2025
@thecrypticace
Copy link
Contributor

Yeah. It needs some tweaks in various spots. Including this bit at the top:

In order for the extension to activate you must have tailwindcss installed and a Tailwind config file named tailwind.config.{js,cjs,mjs,ts,cts,mts} in your workspace.

I'll add this to my list

@thecrypticace thecrypticace changed the title The README.md file eneds updating for v4. The README.md file needs updating for v4. Feb 21, 2025
@adambirds
Copy link
Author

Yeah. It needs some tweaks in various spots. Including this bit at the top:

In order for the extension to activate you must have tailwindcss installed and a Tailwind config file named tailwind.config.{js,cjs,mjs,ts,cts,mts} in your workspace.

I'll add this to my list

Yeah this is the one. Just isn't clear that it supports v4 yet!

@andradei
Copy link

Does it work without the presence of the tailwind.config.js (or one the alternaticves) file?

@thecrypticace
Copy link
Contributor

It does, yes.

@qingzhoufeihu
Copy link

In Tailwind v4, there is no tailwind.config.js, and the plugins do not provide suggestions. How can this be resolved?

@andradei
Copy link

andradei commented Mar 9, 2025

On the LSP, it is a matter of setting an arbitrary root directory. For me, I assigned a tailwind.css file at the root that the LSP uses to identify the root dir of my project.

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

Successfully merging a pull request may close this issue.

5 participants