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.
Updated Tailwind v3 to v4 by following the upgrade guide and manually changing a couple of styles.
Manual upgrade steps:
npx @tailwindcss/upgrade@next
tailwind.config.js
totailwind.css
@theme
config and modifications to@layer base
prism.css
and add@reference "./tailwind.css";
to the top of the file.tailwind.config.js
to use the new css variable format e.g.colors.primary.500
tocolor-primary-500
letterSpacing.tight
intailwind.config.js
has been changed to--tracking-tight
borderRadius.DEFAULT
is now--radius-sm
intailwind.css
bg-green-500 bg-opacity-20
tobg-green-500/20
. Affectsprism.css
and a couple of other components.moduleResolution
intsconfig.json
to "bundler". Add "pliny/": ["node_modules/pliny/"] to tsconfig.json path.This PR also pins React to v19 and upgraded a couple of dependencies.
There's a slight change in style as the color palette has been updated and some of the tokens has also been modified but I think those are relatively minor and I did not update them.
Close #1103