-
Notifications
You must be signed in to change notification settings - Fork 195
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
Extension Not Starting #783
Comments
Hey! What version of VS Code are you using? And what type of project? Next, Svelte, something else? |
Also, one other thing that would be useful is a list of all installed extensions if you could provide that ( |
Thanks for the q's. I'm using Vite's tooling which uses Rollup. Vscode version is 1.78.2 I'd be happy to try disabling some extensions to help debug. Let me know.
|
This comment was marked as off-topic.
This comment was marked as off-topic.
@albertreed, which folder is your Tailwind config file in? Is it in a folder that is covered by your @Mr-KayJayDee, your issue is unrelated but has been fixed via #787 👍 |
config is |
Thanks! I managed to find the culprit. The Having said that, I don't think that the
So I would recommend updating your "files.exclude": {
- "${workspaceFolder}/shared": true,
+ "shared/**": true,
"client/src/index.css": true,
"moderation-dashboard/**": true,
"node_modules/**": true,
"steam-sdk/**": true
} Hope that helps! |
Thanks! Yes, I noticed that when you asked about files.exclude and added a
note to go back and check that out. Appreciate it! I'll give it a shot in a
few days and report back.
…On Thu, May 25, 2023 at 8:32 AM Brad Cornes ***@***.***> wrote:
Thanks!
I managed to find the culprit. The ${workspaceFolder} placeholder in your
files.exclude configuration was causing the issue. I have pushed a fix
that should ensure that the extension can still activate when placeholders
are used.
Having said that, I don't think that the workspaceFolder placeholder is
actually available in the files.exclude setting. This placeholder is only
available in certain settings (
https://code.visualstudio.com/docs/editor/variables-reference#_is-variable-substitution-supported-in-user-and-workspace-settings),
and in files.exclude it is redundant anyway because the paths are already
resolved relative to the workspace folder:
*The glob patterns in [the files.exclude and search.exclude] settings are
always evaluated relative to the path of the workspace folder.* (source
<https://code.visualstudio.com/docs/editor/codebasics#_advanced-search-options>
)
So I would recommend updating your files.exclude setting, and this should
fix your issue:
"files.exclude": {- "${workspaceFolder}/shared": true,+ "shared/**": true,
"client/src/index.css": true,
"moderation-dashboard/**": true,
"node_modules/**": true,
"steam-sdk/**": true
}
Hope that helps!
—
Reply to this email directly, view it on GitHub
<#783 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABFAOK4LY6L2VRFOHDBLDJTXH5GPNANCNFSM6AAAAAAYFEGKTE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
What version of Tailwind CSS IntelliSense are you using?
0.9.11
What version of Tailwind CSS are you using?
3.3.2
What package manager are you using?
yarn
What operating system are you using?
Mac
Tailwind config
VS Code settings
Workspace
User
Reproduction URL
Unfortunately, not something I can provide. Of course, free to close the issue if that makes this not useful.
Describe your issue
I think the extension is not starting at all, though I'm not sure how to debug that. cmd->shift->p->"tailwind" fails to show anything at all. In the output pane, I do not see tailwinds listed in the pulldown.
Within the extension pane, if I got to the "Runtime Status" pane, I see this
It's a large project in a monorep. The client and tailwinds.config.js lives within a subfolder of the workspace root.
The text was updated successfully, but these errors were encountered: