Skip to content

Commit f4225ce

Browse files
Update readme
Co-authored-by: Jonathan Reinink <[email protected]>
1 parent 6545d13 commit f4225ce

File tree

1 file changed

+15
-8
lines changed

1 file changed

+15
-8
lines changed

packages/vscode-tailwindcss/README.md

Lines changed: 15 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -164,19 +164,24 @@ Enable the Node.js inspector agent for the language server and listen on the spe
164164

165165
**Default: `null`**
166166

167-
By default the extension scans your project for CSS files and determines your "root" CSS file when looking for a Tailwind CSS v4 project. Likewise, for v3 projects, the extension will automatically use the first `tailwind.config.{js,cjs,mjs,ts,cts,mts}` file that it can find.
167+
This setting allows you to manually specify the CSS entrypoints (for v4 projects) or the Tailwind configuration file (for v3 projects). By default, the extension attempts to detect your project setup automatically:
168168

169-
If IntelliSense is unable to detect your project you can use this setting to manually specify the CSS files (for v4) or config file(s) (for v3) yourself instead.
169+
- **For Tailwind CSS v4**: The extension scans your project for CSS files and determines the "root" CSS file.
170+
- **For Tailwind CSS v3 (and earlier)**: The extension automatically uses the first `tailwind.config.{js,cjs,mjs,ts,cts,mts}` file it finds.
170171

171-
#### v4.x
172+
If IntelliSense is unable to detect your project, you can use this setting to define your config files manually.
172173

173-
If your project contains a single CSS entrypoint you can specify a string value:
174+
#### Tailwind CSS v4.x (CSS entrypoints)
175+
176+
For v4 projects, specify the CSS file(s) that serve as your Tailwind entrypoints.
177+
178+
If your project contains a single CSS entrypoint, set this option to a string:
174179

175180
```json
176181
"tailwindCSS.experimental.configFile": "src/styles/app.css"
177182
```
178183

179-
For projects with multiple CSS entrypoints use an object where each key is a file path and each value is a glob pattern (or array of glob patterns) representing the set of files that the file applies to:
184+
For projects with multiple CSS entrypoints, use an object where each key is a file path and each value is a glob pattern (or array of patterns) representing the files it applies to:
180185

181186
```json
182187
"tailwindCSS.experimental.configFile": {
@@ -185,15 +190,17 @@ For projects with multiple CSS entrypoints use an object where each key is a fil
185190
}
186191
```
187192

188-
#### v3.x and below
193+
#### Tailwind CSS v3.x and earlier (config files)
194+
195+
For v3 projects and below, specify the Tailwind configuration file(s) instead.
189196

190-
If your project contains a single Tailwind config file you can specify a string value:
197+
If your project contains a single Tailwind config, set this option to a string:
191198

192199
```json
193200
"tailwindCSS.experimental.configFile": ".config/tailwind.config.js"
194201
```
195202

196-
For projects with multiple config files use an object where each key is a config file path and each value is a glob pattern (or array of glob patterns) representing the set of files that the config file applies to:
203+
For projects with multiple config files, use an object where each key is a config file path and each value is a glob pattern (or array of patterns) representing the files it applies to:
197204

198205
```json
199206
"tailwindCSS.experimental.configFile": {

0 commit comments

Comments
 (0)