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
Provides syntax definitions so that Tailwind features are highlighted correctly.
34
-
35
31
### Tailwind CSS Language Mode
36
32
37
-
An alternative to VS Code's built-in CSS language mode which maintains full CSS IntelliSense support even when using Tailwind-specific at-rules.
33
+
An alternative to VS Code's built-in CSS language mode which maintains full CSS IntelliSense support even when using Tailwind-specific at-rules. Syntax definitions are also provided so that Tailwind-specific syntax is highlighted correctly in all CSS contexts.
38
34
39
35
## Recommended VS Code Settings
40
36
41
-
VS Code has built-in CSS validation which may display errors when using Tailwind-specific at-rules, such as `@apply`. You can disable this with the `css.validate` setting:
42
-
43
-
```
44
-
"css.validate": false
45
-
```
37
+
### `files.associations`
46
38
47
-
Alternatively, you can configure VS Code to use the provided Tailwind CSS language mode by default for all CSS files:
39
+
Use the `files.associations` setting to tell VS Code to always open `.css` files in Tailwind CSS mode:
48
40
49
41
```
50
42
"files.associations": {
51
43
"*.css": "tailwindcss"
52
44
}
53
45
```
54
46
47
+
### `editor.quickSuggestions`
48
+
55
49
By default VS Code will not trigger completions when editing "string" content, for example within JSX attribute values. Updating the `editor.quickSuggestions` setting may improve your experience:
0 commit comments