-
Notifications
You must be signed in to change notification settings - Fork 194
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
0.4.1 broke class suggestions when TW config not in project root #159
Comments
Are you still seeing this issue @mmirus? |
Thanks for following up, @bradlc! Unfortunately, yes, still hitting this. Please let me know if I can help test things / provide additional information, and I'll do my best to give you a hand! |
Are you able to share the repository of a project where this is happening? If not please could you let me know which package manager you are using, and if possible a summary of how your project is structured, in particular the location of |
I can't share the repository, unfortunately. Here's a cleaned up version of the folder structure with some notes. In reality there are way, way more folders and files--but the path down to the TW config,
Edit: Oh, and using npm for package management! |
Thanks for that! I tried to reproduce with no luck. I have added some basic logging to the new release ( |
Ooooh, that gives some output that looks like it will be helpful--thank you!
(I think that first failure right at the top showed up b/c the editor opened to a file that was outside the area that has TW; after that, I believe the output is from when I switched to a file inside the area with TW.) In our
And under
I have verified that When I open the
Finally, when I change
The extension initializes successfully when vscode is opened from the project root. So it seems like maybe either tailwind itself or the vscode extension has trouble finding |
Hey guys,
|
Working for me now with 0.5.4! Thank you, @bradlc! Really appreciate your work on this. |
I'm seeing the issue ('...No Tailwind CSS config found') when my tailwind.config is in a directory with a |
It seems like 0.4.1 broke class suggestions for me when my Tailwind config file is not in the workspace root.
My config is in a subfolder within the project, and previously the extension suggested class names without any trouble. This stopped working recently, and I found today that I can fix the problem by doing either of the following:
Happy to provide any additional info that would be helpful or do testing/troubleshooting for you!
Thanks!
Version: 1.47.3
Commit: 91899dcef7b8110878ea59626991a18c8a6a1b3e
Date: 2020-07-23T15:51:39.791Z
Electron: 7.3.2
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Linux x64 5.4.53-1-MANJARO
The text was updated successfully, but these errors were encountered: