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

chore(deps): update dependency tw-colors to v3 #71

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 4, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
tw-colors 2.0.3 -> 3.3.2 age adoption passing confidence

Release Notes

L-Blondy/tw-colors (tw-colors)

v3.3.2

Compare Source

Fixed
  • [#​44] - Fixes typescript error when using the option "exactOptionalPropertyTypes": true

v3.3.1

Compare Source

v3.3.0

Compare Source

Added
  • Added support for prefers-color-scheme

v3.2.0

Compare Source

Fixed
  • [#​30] - The colors defined via the plugin now properly override tailwind's default colors in case of name clash.
Breaking changes:
  • NativeWind 2 with Next.js is no longer supported

v3.1.2

Compare Source

Fixed
  • Fixed intellisense for the theme class

v3.1.1

Compare Source

v3.1.0

Compare Source

Fixed
  • [#​26] - NativeWind 2 with the Next.js setup is now supported.

v3.0.3

Compare Source

Added
  • Added support for group modifiers with theme variants

v3.0.2

Compare Source

v3.0.1

Compare Source

v3.0.0

Compare Source

Added
  • The variants can now be declared anywhere without having to redeclare the theme.
  • New option produceThemeVariant to customize the variant names. It will fallback to produceThemeClass if omitted
breaking changes:
  • Renamed the option getCssVariable to produceCssVariable.
  • Renamed the option getThemeClassName to produceThemeClass. The default return value is now the themeName instead of theme-${themeName}

v2.2.0

Compare Source

Added
  • strict option. If false (default) invalid colors are ignored, if true invalid colors throw an error

v2.1.1

Compare Source

Fixed
  • Fixed a typescript error when using a functional config and the defaultTheme option

v2.1.0

Compare Source

breaking changes:
  • resolveConfig was renamed to resolveTwcConfig
  • Only two types are exposed: TwcConfig and TwcOptions, corresponding to createThemes(TwcConfig, TwcOptions) and resolveTwcConfig(TwcConfig, TwcOptions). Previously exposed types are no longer valid.
Added
  • defaultTheme option

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@vercel
Copy link

vercel bot commented Sep 4, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
usa ✅ Ready (Inspect) Visit Preview 💬 Add feedback Sep 4, 2024 2:02pm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
📦️ build Build system or dependency changes. 🤖 renovate Changes by renovate.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants