v3.0.0-alpha.2

[adamwathan]

To upgrade, install tailwindcss@next:

npm install -D tailwindcss@next

If you're using @tailwindcss/typography, you'll want to update that package as well:

npm install -D @tailwindcss/typography@next

Remember this is an alpha release, so some things might be broken. I don't know about them otherwise I would have fixed them, but you are gonna find them! So try it, break it, and tell me about it when you do so we can get this thing really battle-tested for a proper v3.0 release in a few weeks.

---

Changed

• Don't use pointer cursor on disabled buttons by default (#5772)
• Set default content value in preflight instead of within each before/after utility (#5820)
• Remove prefix as a function (#5829)

Added

• Add flex-basis utilities (#5671)
• Make negative values a first-class feature (#5709)
• Add fit-content values for min/max-width/height utilities (#5638)
• Add min/max-content values for min/max-height utilities (#5729)
• Add all standard cursor-* values by default (#5734)
• Add grow-* and shrink-* utilities, deprecate flex-grow-* and flex-shrink-* (#5733)
• Add text-decoration-color utilities (#5760)
• Add new declarative addVariant API (#5809)
• Add first-class print variant for targeting printed media (#5885)
• Add full color palette for fill-* and stroke-* utilities (Add full color palette for fill/stroke #5933)
• Add composable API for colored box shadows (#5979)

Fixed

• Configure chokidar's awaitWriteFinish setting to avoid occasional stale builds on Windows (#5774)
• Fix CLI --content option (#5775)
• Fix before/after utilities overriding custom content values at larger breakpoints (#5820)
• Cleanup duplicate properties (#5830)
• Allow _ inside url() when using arbitrary values (#5853)
• Prevent crashes when using comments in @layer AtRules (#5854)
• Handle color transformations properly with theme(...) for all relevant plugins (#4533, #5871)
• Ensure @apply-ing a utility with multiple definitions works (#5870)

---

Thanks to everyone who contributed to this release: @adamwathan, @bradlc, @dance2die, @dcastil, @DoctorDerek, @hardfist, @lukewarlow, @MatteoGauthier, @MichaelAllenWarner, @nifte, @reinink, @RobinMalfait, @sachinraja, @xzfd1010 ❤️

---

This discussion was created from the release v3.0.0-alpha.2.

[surjithctly]

How about adding border-3 when border-2 is not enough and border-4 is too much.

[RobinMalfait]

Hey! Thank you for your suggestion!
Much appreciated! 🙏

You can extend your config if you want this behaviour: https://tailwindcss.com/docs/border-width#border-widths

[TaylorWatson]

Is there docs for v3? Even if uncompleted and possibly old information, so people who want to just mess around can at least somewhat navigate in the dark on new features?

[yevheniimoskalenko1]

@adamwathan I have error with typography

[kkgthb]

Could there be more than text-decoration-color for text-decoration? Like sizing & placement? It'd be nice to be able to do tricks along the lines of this in native Tailwind. I thought maybe I saw some energy in that direction: #2050 (comment)

[reinink]

Yes 😎

Text Decoration Color
Text Decoration Style
Text Decoration Thickness
Text Underline Offset

[spencerwmiles]

Was the release of V3 intentional or some sort of error? By the sounds of this announcement it was not intended to drop for a couple more weeks but it's now available via @latest tag as of ~2 hours ago.

Just wanting to be sure before locking in V3 related changes in a project right now.

[dcastil]

I think this was intentional. See this Tweet from Adam a couple days ago. https://twitter.com/adamwathan/status/1467915766343348228