Skip to content

Commit 25e3a3b

Browse files
committed
doc: remove plugins note from README
See thread at #450 (comment), the default plugins are still present. [skip ci]
1 parent 780846c commit 25e3a3b

File tree

1 file changed

+0
-8
lines changed

1 file changed

+0
-8
lines changed

Diff for: README.md

-8
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,6 @@
1212
- [Upgrading your application from Tailwind v3 to v4](#upgrading-your-application-from-tailwind-v3-to-v4)
1313
* [You don't _have_ to upgrade](#you-dont-_have_-to-upgrade)
1414
* [Upgrade steps](#upgrade-steps)
15-
* [Plugins](#plugins)
1615
* [Troubleshooting](#troubleshooting)
1716
- [Developing with Tailwindcss](#developing-with-tailwindcss)
1817
* [Configuration and commands](#configuration-and-commands)
@@ -152,13 +151,6 @@ Done in 56ms
152151
If this doesn't succeed, it's likely that you've customized your Tailwind configuration and you'll need to do some work to make sure your application upgrades. Please read the [official upgrade guide](https://tailwindcss.com/docs/upgrade-guide)!
153152
154153
155-
### Plugins
156-
157-
In Tailwind CLI v3, some Tailwind plugins were included by default in the CLI tool. However, in v4 these default plugins have been removed.
158-
159-
In order to use any plugins with v4, either by declaring them in your (optional) config file or using the [`@plugin` directive](https://tailwindcss.com/docs/functions-and-directives#plugin-directive), it's necessary to install them using a local javascript package manager.
160-
161-
162154
### Troubleshooting
163155
164156
You may want to check out [TailwindCSS v4 - upgrade experience report · rails/tailwindcss-rails · Discussion #450](https://github.com/rails/tailwindcss-rails/discussions/450) if you're having trouble upgrading.

0 commit comments

Comments
 (0)