Bump tailwindcss from 1.2.0 to 1.9.6

[dependabot-preview]

Bumps tailwindcss from 1.2.0 to 1.9.6.

Release notes

Sourced from tailwindcss's releases.

v1.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.

v1.9.5

Fixed

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

v1.9.4

Fixed

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

v1.9.3

• Fix issue where tailwindcss init --full scaffolded a corrupt config file (tailwindlabs/tailwindcss#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.

v1.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

v1.9.1

Fixed

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

v1.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)

Changelog

Sourced from tailwindcss's changelog.

[1.9.6] - 2020-10-23

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.

[2.0.0-alpha.1] - 2020-10-20

Added

• Added dark mode support (#2279, #2631)
• Added overflow-ellipsis and overflow-clip utilities (#1289)
• Add transform-gpu to force hardware acceleration on transforms when beneficial (#1380)
• Extended spacing scale (#2630)
• Add spacing scale to inset plugin (#2630)
• Enable useful relative sizes for more plugins (#2630)
• Extend font size scale (#2609, #2619)
• Support using @apply with complex classes (#2159)
• Add new 2xl breakpoint (#2609)
• Add default line-height values for font-size utilities (#2609)
• Support defining theme values using arrays wherever it makes sense (box-shadow, transition-property, etc.) (e13f083c4)
• Enable group-hover for color utilities by default (28985b6)
• Enable focus for z-index utilities by default (ae5b3d3)

Changed

• New @apply implementation, slight backwards incompatibilities with previous behavior (#2159)
• Move truncate class to textOverflow core plugin (#2562)
• Removed target feature and dropped any compatibility with IE 11 (#2571)
• Switch normalize.css to modern-normalize (#2572)
• Remove scrolling-touch and scrolling-auto utilities (#2573)
• Change special use of 'default' in config to 'DEFAULT' (#2580)
• Drop support for Node 8 and 10 (#2582)
• Modernize default system font stacks (#1711)
• Upgrade to PurgeCSS 3.0
• Upgrade to PostCSS 8.0 Reverted for now
• Use logical properties for space and divide utilities (#1883)
• Make theme retrieve the expected resolved value when theme value is complex (e13f083c4)
• Adjust default font-size scale to include 60px instead of 64px (#2619)
• Update default colors in Preflight to match new color palette (#2633)

[1.9.5] - 2020-10-19

Fixed

• Fix issue where using theme with default line-heights did not resolve correctly

[1.9.4] - 2020-10-17

Commits

• 8f3dbfe 1.9.6
• 29946ae Update changelog
• bf77f29 Fix style
• cf8596b Include default config by default in presets (#2662)
• a350ef0 1.9.5
• d371f46 Update changelog
• 15ae28a Fix issue where using theme with default line-heights did not resolve corre...
• a2c6dcc 1.9.4
• d6fb40d Update changelog
• d371727 Ensure changes to withOptions plugins trigger rebuilds
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot will not automatically merge this PR because it includes an out-of-range update to a production dependency.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in the .dependabot/config.yml file in this repo:

• Update frequency
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

[dependabot-preview]

The following labels could not be found: dependencies.