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

fix(deps): update dependency @tailwindcss/typography to v0.4.1 #10

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

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Nov 27, 2020

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@tailwindcss/typography 0.2.0 -> 0.4.1 age adoption passing confidence

Release Notes

tailwindcss/typography

v0.4.1

Compare Source

Fixed

  • Fix list-style modifier selectors (#​137)

v0.4.0

Compare Source

Fixed

  • Colors without 600 variant, breaks everything (#​107)
  • Fix empty line in firefox for pre code tags (#​125)

Added

  • Add support for the start and reversed attribute on ol elements (#​110)
  • Add support for the type on ul and ol elements (#​126)

Changed (internal)

v0.3.1

Compare Source

v0.3.0

Compare Source

This release drops support for Tailwind CSS v1.0.

Some of the changes needed to support Tailwind CSS v2.0 necessitate dropping support for v1.0. You should stay on v0.2.0 until you can upgrade your projects to Tailwind CSS v2.0.

Read the Tailwind CSS v2.0 upgrade guide for information on upgrading your projects.

Changed

  • Add support for Tailwind CSS v2.0 and drops support for v1.0 (#​79, #​82, #​87)
  • Use extend for any overrides, assigning directly to theme.typography now completely overrides default configuration
  • Consistently use ::before instead of :before (ba33d77)
  • Read color values from the user's theme instead of only the default theme

Added

  • Add new className option for overriding prose class (#​28)
  • Add color modifiers by default like prose-blue for setting link styles (#​92)

Upgrading from v0.2.0 to v0.3.0

This version of the plugin is designed for Tailwind CSS v2.0. Make sure you upgrade Tailwind before upgrading this plugin.

Customizations should be moved under extend, default should become DEFAULT

The biggest difference is that any customizations you had under theme.typography should be moved to theme.extend.typography, and the default key should be uppercased to DEFAULT:

  module.exports = {
    theme: {
-     typography: {
-       default: {
-         css: {
-           color: theme("colors.gray.700"),
-           '[class~="lead"]': {
-             color: theme("colors.gray.600"),
-           },
-           a: {
-             color: theme("colors.indigo.600"),
-             fontWeight: 600,
-             textDecoration: "none",
-           },
-         },
-       },
-     },
+     extend: {
+       typography: {
+         DEFAULT: {
+           css: {
+             color: theme("colors.gray.700"),
+             '[class~="lead"]': {
+               color: theme("colors.gray.600"),
+             },
+             a: {
+               color: theme("colors.indigo.600"),
+               fontWeight: 600,
+               textDecoration: "none",
+             },
+           },
+         },
+       },
+     },
    },
  };

Any customizations directly under theme.typography will now completely replace the defaults, which is consistent with how theme modification generally works in Tailwind.

Colors are read from theme by default

In previous versions, all of the colors used by this plugin were read from Tailwind's default theme rather than from your theme. The plugin now looks for colors in your theme first, falling back to the defaults if they don't exist. So if the plugin is looking for gray.700 for the main body color, it will use your defined gray.700 if present, or fall back to the default one.

If your colors are totally custom and the numbers don't line up with Tailwind's defaults from a contrast perspective, you probably won't get good results out of the box. In this case you should manually override the colors like you were likely already doing using the existing customization API.


Configuration

📅 Schedule: 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 has been generated by WhiteSource Renovate. View repository job log here.

@vercel
Copy link

vercel bot commented Nov 27, 2020

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/toni783/nuxt-storyblok-intro/3hriKV7RiunRYnq9AuxGvSv2J1KW
✅ Preview: https://nuxt-storyblok-git-renovate-tailwindcss-typography-0x-6c07f4.vercel.app

@renovate renovate bot force-pushed the renovate/tailwindcss-typography-0.x branch from 1768dc9 to 5750644 Compare January 24, 2021 09:59
@renovate renovate bot changed the title fix(deps): update dependency @tailwindcss/typography to v0.3.1 fix(deps): update dependency @tailwindcss/typography to v0.4.0 Jan 24, 2021
@renovate renovate bot force-pushed the renovate/tailwindcss-typography-0.x branch from 5750644 to 1e3b510 Compare June 6, 2021 22:57
@renovate renovate bot changed the title fix(deps): update dependency @tailwindcss/typography to v0.4.0 fix(deps): update dependency @tailwindcss/typography to v0.4.1 Jun 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant