Replies: 1 comment
|
Yes, this can happen with Bun isolated installs. The Tailwind CSS IntelliSense extension resolves the Tailwind package by looking for it in the workspace dependency tree (usually through A couple of workarounds: 1. Explicitly set the Tailwind config path in VS Code settings "tailwindCSS.experimental.configFile": "./tailwind.config.ts"2. Ensure Tailwind is installed in the workspace where IntelliSense runs 3. Restart the Tailwind IntelliSense server If it still doesn't resolve correctly, it’s likely due to how the extension currently resolves dependencies and may need improved support for Bun’s isolated install structure. |
Uh oh!
There was an error while loading. Please reload this page.
i have a bun monorepo and when using isolated installs the tailwind intellisense is not working
if changing to hoisted installs they it works correctly
maybe the tailwind extensions is not finding the tailwind package (because isolated installs symlink packages)?
All reactions