nathancahill / split

Unopinionated utilities for resizeable split views
https://split.js.org/
MIT License
6.15k stars 450 forks source link

Bump tailwindcss from 2.1.1 to 2.2.3 #648

Closed dependabot-preview[bot] closed 3 years ago

dependabot-preview[bot] commented 3 years ago

Bumps tailwindcss from 2.1.1 to 2.2.3.

Release notes

Sourced from tailwindcss's releases.

v2.2.3

Added

  • Pass extended color palette to theme closures so it can be used without installing Tailwind when using npx tailwindcss (359252c)

Fixed

  • JIT: Explicitly error when - is used as a custom separator (#4704)
  • JIT: Don't add multiple ~ when stacking peer-* variants (#4757)
  • Remove outdated focus style fix in Preflight (#4780)
  • Enable purge if provided on the CLI (#4772)
  • JIT: Fix error when not using a config file with postcss-cli (#4773)
  • Fix issue with resolveConfig not being importable in Next.js pags (#4725)

v2.2.2

Fixed

  • JIT: Reintroduce transform, filter, and backdrop-filter classes purely to create stacking contexts to minimize the impact of the breaking change (#4700)

v2.2.1

Fixed

  • Recover from errors gracefully in CLI watch mode (#4693)
  • Fix issue with media queries not being generated properly when using PostCSS 7 (#4695)

v2.2.0

Tailwind CSS v2.2.0

Six weeks ago I didn't even have v2.2 on my roadmap and yet somehow here we are today, with one of the biggest Tailwind CSS feature releases of all-time?!

This release is loaded with tons of cool new stuff, mostly targeting the new Just-in-Time mode which unlocks so many cool ideas we probably couldn't have pulled off if we had to keep being mindful of the CSS file size in development.

To upgrade, install the latest version via npm:

npm install -D tailwindcss@latest

Note that we've had to make a couple small changes to the JIT engine as we've added features, fixed bugs, and improved the overall reliability, so make sure to read about the changes and deprecations when upgrading if you are using just-in-time mode.

... (truncated)

Changelog

Sourced from tailwindcss's changelog.

[2.2.3] - 2021-06-23

Added

  • Pass extended color palette to theme closures so it can be used without installing Tailwind when using npx tailwindcss (359252c)

Fixed

  • JIT: Explicitly error when - is used as a custom separator (#4704)
  • JIT: Don't add multiple ~ when stacking peer-* variants (#4757)
  • Remove outdated focus style fix in Preflight (#4780)
  • Enable purge if provided on the CLI (#4772)
  • JIT: Fix error when not using a config file with postcss-cli (#4773)
  • Fix issue with resolveConfig not being importable in Next.js pags (#4725)

[2.2.2] - 2021-06-18

Fixed

  • JIT: Reintroduce transform, filter, and backdrop-filter classes purely to create stacking contexts to minimize the impact of the breaking change (#4700)

[2.2.1] - 2021-06-18

Fixed

  • Recover from errors gracefully in CLI watch mode (#4693)
  • Fix issue with media queries not being generated properly when using PostCSS 7 (#4695)

[2.2.0] - 2021-06-17

Changed

  • JIT: Use "tracking" context by default instead of "watching" context for improved reliability with most bundlers (#4514)

    Depending on which tooling you use, you may need to explicitly set TAILWIND_MODE=watch until your build runner has been updated to support PostCSS's dir-dependency message type.

Added

  • Add background-origin utilities (#4117)
  • Improve @apply performance in projects that process many CSS sources (#3178)
  • JIT: Don't use CSS variables for color utilities if color opacity utilities are disabled (#3984)
  • JIT: Redesign matchUtilities API to make it more suitable for third-party use (#4232)
  • JIT: Support applying important utility variants (#4260)
  • JIT: Support coercing arbitrary values when the type isn't detectable (#4263)
  • JIT: Support for raw syntax in purge config (#4272)
  • Add empty variant (#3298)
  • Update modern-normalize to v1.1 (#4287)
  • Implement theme function internally, remove postcss-functions dependency (#4317)
  • Add screen function to improve nesting plugin compatibility (#4318)
  • JIT: Add universal shorthand color opacity syntax (#4348)

... (truncated)

Commits


Dependabot compatibility score

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.

If all status checks pass Dependabot will automatically merge this pull request.


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 ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@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[bot] commented 3 years ago

One of your CI runs failed on this pull request, so Dependabot won't merge it.

Dependabot will still automatically merge this pull request if you amend it and your tests pass.

dependabot-preview[bot] commented 3 years ago

Superseded by #649.