lsp-tailwindcss not activate in monorepo with tailwind-workspace-preset.js

[kermorgant]

Hi,

In a monorepo setup based on nx with separate next.js apps sharing a central tailwind-workspace-preset.js (inspired by this doc), lsp-tailwindcss often fails to activate because many css files don't have any parent folder containing tailwind.config.js.

Maybe adding an customizable var to allow per project definition of what filke triggers activation would be a good addition ?
(For now, I've just added a symlink to have a tailwind.config.js in project root)

[merrickluo]

Thanks for the info, I originally added this check because the language server seems to require it, if it works fine, maybe this should be removed.

[kermorgant]

Ah, if the language server requires it, then this check probably makes sense (my solution was to create this tailwind.config.js file as a symlink)

…

On Thu, 10 Mar 2022, 05:34 A.I., ***@***.***> wrote: Thanks for the info, I originally added this check because the language server seems to require it, if it works fine, maybe this should be removed. — Reply to this email directly, view it on GitHub <#35 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACQSQLAQDCQTDSMKMOSE6MTU7FUSZANCNFSM5OGNK7VA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: ***@***.***>