[Snyk] Upgrade tailwindcss from 1.1.2 to 1.9.6 #17
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Snyk has created this PR to upgrade tailwindcss from 1.1.2 to 1.9.6.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
Release notes
Package name: tailwindcss
Changed
The
presets
feature had unexpected behavior where a preset config without its ownpresets
key would not extend the default config. (#2662)If you were depending on this unexpected behavior, just add
presets: []
to your own preset to exclude the default configuration.Fixed
theme
with default line-heights did not resolve correctly (#2308)Fixed
withOptions
API would not trigger rebuilds in watch processestailwindcss init --full
scaffolded a corrupt config file (#2556)I've opted to remove the console notices about upcoming breaking changes (that encouraged users to opt-in to future features using the
future
option in their config file.)While I had good intentions for this approach originally, I'm realizing now that it just ends up creating more confusion and a sloppier documentation story. Any breaking changes can't really be documented easily because the documentation needs to show the stable version of any given feature, since we can't assume someone has opted in to the new stuff.
This means that when someone does opt in, they are basically opting in to being out of sync with the documentation, which is a crappy experience for them, especially if they can't upgrade to Tailwind 2.0 in the near future because they need to support IE11.
For this reason I've decided to stop warning about the upcoming breaking changes so that we don't force users to opt-in to an essentially undocumented version of the framework. Instead we will continue to maintain the "upcoming changes" page in the docs, and continue to ship new ideas behind flags for people to test but without the nudge to upgrade. Folks who are comfortable opting-in to the new stuff early can do so, and folks that aren't can comfortably keep using things the way they are (along with complete documentation) and upgrade to the next version all at once, like people have done traditionally with most dependencies.
I will always strive to make breaking changes as painless and minimal as possible, so spending an hour to do the upgrade in one sitting is never going to be too bad. I highly value backwards compatibility and will never make needlessly breaking changes. An improvement is only worth making if it improves things enough to make up for the upgrade cost, and that's usually pretty rare. For example
lh-5
might be a nicer class name thanleading-5
but it is absolutely not worth breaking everyone's muscle memory and forcing them to replace hundreds of instances of classes in their projects. We'll only make breaking changes if they unlock meaningful new possibilities or fix fundamental problems that are holding people back.Fixed
word-wrap
andoverflow-wrap
together, not one or the other sinceword-wrap
is IE-onlyFixed
corePlugins
inresolveConfig
to avoid bundling browser-incompatible code (#2548)Tailwind CSS v1.9 is now available with a new
presets
feature, some new utilities, and a few accessibility improvements. Check it out!New features
presets
config option (#2474)tailwind.config.js
files with availablefuture
flags commented out (#2379)col-span-full
androw-span-full
(#2471)outline
configurable,outline-none
more accessible by default, and addoutline-black
andoutline-white
(#2460)rotate
andskew
values (#2528)xl
,2xl
, and3xl
border radius values (#2529)grid-auto-columns
andgrid-auto-rows
(#2531)defaultLineHeights
andstandardFontWeights
from experimental to futureFixed
word-wrap
instead ofoverflow-wrap
inie11
target mode (#2391)Experimental
2xl
breakpoint (#2468){u}-max-content
and{u}-min-content
utilities to{u}-max
and{u}-min
in experimental extended spacing scale (#2532)Fixed
Fixed
Commit messages
Package name: tailwindcss
Compare
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs