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

Upgrade tailwindcss to v3.1.2 #443

Closed
wants to merge 1 commit into from
Closed

Conversation

lyzadanger
Copy link
Contributor

This version of tailwindcss introduces some additional typing but some
affordances were needed in tsconfig.json and the typing of the
shared tailwind preset to accommodate this.

This version provides more types but required some affordances.
@@ -2,7 +2,7 @@ import plugin from 'tailwindcss/plugin.js';

import colors from 'tailwindcss/colors.js';

export default {
export default /** @type {Partial<import('tailwindcss').Config>} */ ({
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's early days for tailwindcss's type definitions and I was unable to find an appropriate type for a preset , which is what this is, not a full Config. Without the Partial this will gripe about a missing content property, which is indeed required for configs, but not for presets.

Alternately, might be able to type this using Omit, but I'd rather just do this for now and wait for tailwindcss to add a Preset type or similar.

@lyzadanger
Copy link
Contributor Author

🤦🏻‍♀️ failing in CI. I'll look next week.

@lyzadanger
Copy link
Contributor Author

Ah, not my mistake for once: tailwindlabs/tailwindcss#8586

@lyzadanger lyzadanger marked this pull request as draft June 10, 2022 18:48
@lyzadanger
Copy link
Contributor Author

Converting to draft until there is a tailwindcss release that fixes this.

@lyzadanger lyzadanger closed this Jun 16, 2022
@lyzadanger lyzadanger deleted the upgrade-tailwindcss-v3.1.2 branch July 8, 2022 11:52
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.

1 participant