You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe your issue
Got a bit of a unique one for ya. I recently dusted off a repo that I hadn't touched for a few months to find that tailwind intellisense was no longer working when it previously was. After a bunch of troubleshooting, I think I've narrowed down the issue. In short, since extension version 0.9.0 onward, if the file path to the repo has a folder with opening and closing square brackets in the name, the extension never initializes.
Steps to repo:
Take an existing known-good repo with tailwind (or setup a fresh one) and rename its direct parent dir by wrapping the name with square brackets (IE foo -> [foo]). file path should now look something like c:\path\to\[foo]\repoWithTailwind
Open repo in VS Code with intellisense extension v0.9.3 installed
Note that tailwind intellisense doesn't work and Output for the extension ends with "Adding watch patterns" (never gets to "Initializing...")
Close VS Code and rename parent folder to remove square brackets ([foo] -> foo)
Open repo in VS Code again and note tailwind intellisense is back to working as expected
Bonus: Add brackets back to parent folder and downgrade extension to v0.8.7. Note tailwind intellisense works as expected even with square brackets in file path
I didn't include a repro repo because the specific repo/tailwind configuration appears to be irrelevant, just the square brackets in the file path leading to it. But let me know if you would like one, more than happy to set something up!
I realize having folder names with square brackets is unorthodox. For most, the fix would probably be to just rename the offending folder. However for my specific case, I cannot as I am working on UIs for FiveM scripts (Grand Theft Auto 5 modification framework) and unfortunately it requires this strange naming scheme.
I haven't had the chance to take a look at the diff between 0.8.7 and 0.9.0 to see what might be the culprit but I'm guessing it may have something to do with glob handling since square brackets are special characters.
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
What version of Tailwind CSS IntelliSense are you using?
v0.9.3
What version of Tailwind CSS are you using?
v3.2.4
What package manager are you using?
yarn
What operating system are you using?
Repro'd on both macOS & Windows
Tailwind config
VS Code settings
Describe your issue
Got a bit of a unique one for ya. I recently dusted off a repo that I hadn't touched for a few months to find that tailwind intellisense was no longer working when it previously was. After a bunch of troubleshooting, I think I've narrowed down the issue. In short, since extension version 0.9.0 onward, if the file path to the repo has a folder with opening and closing square brackets in the name, the extension never initializes.
Steps to repo:
foo -> [foo]
). file path should now look something likec:\path\to\[foo]\repoWithTailwind
[foo] -> foo
)I realize having folder names with square brackets is unorthodox. For most, the fix would probably be to just rename the offending folder. However for my specific case, I cannot as I am working on UIs for FiveM scripts (Grand Theft Auto 5 modification framework) and unfortunately it requires this strange naming scheme.
I haven't had the chance to take a look at the diff between 0.8.7 and 0.9.0 to see what might be the culprit but I'm guessing it may have something to do with glob handling since square brackets are special characters.
The text was updated successfully, but these errors were encountered: