fix(deps): update dependency @tailwindcss/typography to v0.4.1 #10
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.2.0
->0.4.1
Release Notes
tailwindcss/typography
v0.4.1
Compare Source
Fixed
v0.4.0
Compare Source
Fixed
600
variant, breaks everything (#107)pre code
tags (#125)Added
start
andreversed
attribute onol
elements (#110)type
onul
andol
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
extend
for any overrides, assigning directly totheme.typography
now completely overrides default configuration::before
instead of:before
(ba33d77)Added
className
option for overridingprose
class (#28)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 totheme.extend.typography
, and thedefault
key should be uppercased toDEFAULT
: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 definedgray.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.
This PR has been generated by WhiteSource Renovate. View repository job log here.