Skip to content

Commit 726683e

Browse files
docs: Add link to Safelisting specific utilities from upgrade guide (#2266)
Think it'd be helpful to have the `@source inline` feature mentioned in upgrade guide instead of it just saying `safelist` doesn't exist anymore (this might be a newer feature than when the docs were written). Maybe could've been a little section or something, but wasn't sure how to do it best, and I think like this is better than not at all 🤓 --------- Co-authored-by: Jordan Pittman <[email protected]>
1 parent 312c06c commit 726683e

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/docs/upgrade-guide.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -761,7 +761,7 @@ If you still need to use a JavaScript config file, you can load it explicitly us
761761
@config "../../tailwind.config.js";
762762
```
763763

764-
The `corePlugins`, `safelist`, and `separator` options from the JavaScript-based config are not supported in v4.0.
764+
The `corePlugins`, `safelist`, and `separator` options from the JavaScript-based config are not supported in v4.0. To safelist utilities in v4 use [`@source inline()`](/docs/detecting-classes-in-source-files#safelisting-specific-utilities).
765765

766766
### Theme values in JavaScript
767767

0 commit comments

Comments
 (0)