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
{{ message }}
This repository was archived by the owner on Apr 6, 2021. It is now read-only.
Copy file name to clipboardExpand all lines: README.md
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -36,7 +36,7 @@ Add `@tailwindcss/jit` to your PostCSS configuration instead of `tailwindcss`:
36
36
plugins: {
37
37
- tailwindcss: {},
38
38
+ '@tailwindcss/jit': {},
39
-
autoprefxier: {},
39
+
autoprefixer: {},
40
40
}
41
41
}
42
42
```
@@ -59,9 +59,9 @@ module.exports = {
59
59
60
60
Now start your dev server or build tool as you normally would and you're good to go.
61
61
62
-
> Make sure `NODE_ENV` is set to `development` if you are running a watcher, or Tailwind won't watch your template files for changes. Use `production` for one-off builds.
62
+
> Make sure you set `NODE_ENV=development` if you are running a watcher, or Tailwind won't watch your template files for changes. Set `NODE_ENV=production` for one-off builds.
63
63
>
64
-
> If you want to control whether Tailwind watches files or not more explicitly, set the `TAILWIND_MODE` environment variable to either `watch` or `build`.
64
+
> If you want to control whether Tailwind watches files or not more explicitly, set `TAILWIND_MODE=watch` or `TAILWIND_MODE=build` to override the default `NODE_ENV`-based behavior.
0 commit comments