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.
To prepare for dark mode, it seems useful to upgrade tailwindcss to v2 or v3. I've followed the upgrade guides and prepared two commits, one for the v1 to v2 migration, and one for the v2 to v3 migration.
tailwindcss removed the purgecss dependency with v3, and instead requires a 'content' directive in the config, which is described here:
https://tailwindcss.com/docs/content-configuration
I'm not super sure about that, so it might make sense for someone more experienced to take a look. The rest of the upgrade guide was fairly straightforward. Resulting optical changes seem minimal, the alert boxes are a slightly different shade of yellow, and some grids are spaced a bit differently, that was all I could spot.