Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update tailwindcss: 1.8.10 → 1.9.6 (minor) #18

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

depfu[bot]
Copy link
Contributor

@depfu depfu bot commented Oct 24, 2020


Welcome to Depfu 👋

This is one of the first three pull requests with dependency updates we've sent your way. We tried to start with a few easy patch-level updates. Hopefully your tests will pass and you can merge this pull request without too much risk. This should give you an idea how Depfu works in general.

After you merge your first pull request, we'll send you a few more. We'll never open more than seven PRs at the same time so you're not getting overwhelmed with updates.

Let us know if you have any questions. Thanks so much for giving Depfu a try!


Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ tailwindcss (1.8.10 → 1.9.6) · Repo

Release Notes

1.9.6

Changed

  • The presets feature had unexpected behavior where a preset config without its own presets 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.

1.9.5

Fixed

  • Fix issue where using theme with default line-heights did not resolve correctly (#2308)

1.9.4

Fixed

  • Fix issue changing plugins defined using the withOptions API would not trigger rebuilds in watch processes

1.9.3

  • Fix issue where tailwindcss init --full scaffolded a corrupt config file (#2556)
  • Remove console warnings about upcoming breaking changes (see note below)

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 than leading-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.

1.9.2

Fixed

  • Merge plugins when merging config with preset (#2561
  • Use word-wrap and overflow-wrap together, not one or the other since word-wrap is IE-only

1.9.1

Fixed

  • Don't import corePlugins in resolveConfig to avoid bundling browser-incompatible code (#2548)

1.9.0

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

  • Add new presets config option (#2474)
  • Scaffold new tailwind.config.js files with available future flags commented out (#2379)
  • Add col-span-full and row-span-full (#2471)
  • Make outline configurable, outline-none more accessible by default, and add outline-black and outline-white (#2460)
  • Add additional small rotate and skew values (#2528)
  • Add xl, 2xl, and 3xl border radius values (#2529)
  • Add new utilities for grid-auto-columns and grid-auto-rows (#2531)
  • Promote defaultLineHeights and standardFontWeights from experimental to future

Fixed

  • Don't escape keyframe values (#2432)
  • Use word-wrap instead of overflow-wrap in ie11 target mode (#2391)

Experimental

  • Add experimental 2xl breakpoint (#2468)
  • Rename {u}-max-content and {u}-min-content utilities to {u}-max and {u}-min in experimental extended spacing scale (#2532)
  • Support disabling dark mode variants globally (#2530)

1.8.13

Fixed

  • Support defining colors as closures even when opacity variables are not supported (#2536)

1.8.12

Fixed

  • Reset color opacity variable in utilities generated using closure colors (#2515)

1.8.11

  • Make tailwindcss.plugin work in ESM environments for reasons

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 56 commits:

🆕 @​babel/core (added, 7.12.3)

🆕 @​storybook/addon-actions (added, 6.0.27)

🆕 @​storybook/addon-essentials (added, 6.0.27)

🆕 @​storybook/addon-links (added, 6.0.27)

🆕 @​storybook/html (added, 6.0.27)

🆕 axios (added, 0.20.0)

🆕 babel-loader (added, 8.1.0)

🆕 react-is (added, 16.13.1)


Depfu Status

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands
@​depfu rebase
Rebases against your default branch and redoes this update
@​depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@​depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@​depfu close
Closes this PR and deletes the branch
@​depfu reopen
Restores the branch and reopens this PR (if it's closed)
@​depfu pause
Ignores all future updates for this dependency and closes this PR
@​depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@​depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants