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

How to force start in monorepo #33

Open
AkisArou opened this issue Jan 12, 2024 · 1 comment
Open

How to force start in monorepo #33

AkisArou opened this issue Jan 12, 2024 · 1 comment

Comments

@AkisArou
Copy link

AkisArou commented Jan 12, 2024

I have a monorepo that does not have a tailwind.config.js/ts file at the root.
I have packages that do have a config, and the language server works fine.
But other packages that do not have, and still have tsx files, I do not have intellisense.
When adding a dummy tailwind.config.js file at the root, it does work, but when I am into a package that has a nested config file, I do not have intellisense for the custom colors etc.
:CocCommand tailwindCSS.forceActivate as you mentioned in another issue, do not exist anymore.
How can I have default tailwind intellisense for common classes in packages that do not have a config file?
And when I am in a package that does have, use this.
Is force starting the language server even without a found config file possible to get intellisense?
Thanks!

Edit: In nvim-lspconfig I can do the following: tailwindCSS.experimental.configFile
but does not exist in coc-tailwindcss3

@phaabe
Copy link

phaabe commented Apr 1, 2024

I am interested in something similar. It should be working in an index.html file with a header like
<script src="https://cdn.tailwindcss.com"></script> .

Workaround for now though: add a tailwind config file.

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

2 participants