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

type: the opacity of tailwind's custom keyframes cannot be a number. #14247

Open
HydenLiu opened this issue Aug 24, 2024 · 2 comments
Open

type: the opacity of tailwind's custom keyframes cannot be a number. #14247

HydenLiu opened this issue Aug 24, 2024 · 2 comments

Comments

@HydenLiu
Copy link

What version of Tailwind CSS are you using?

v3.4.10

What build tool (or framework if it abstracts the build tool) are you using?

For example: postcss-cli 8.3.1, Next.js 10.0.9, webpack 5.28.0

What version of Node.js are you using?

For example: v12.0.0

What browser are you using?

For example: Chrome, Safari, or N/A

What operating system are you using?

macOS

Reproduction URL

https://play.tailwindcss.com/ks4NiyjRok?file=config

Describe your issue

The opacity of tailwind's custom keyframes cannot be a number.
image

@wongjn
Copy link
Contributor

wongjn commented Aug 24, 2024

As a work-around, you could have the values as strings and it shouldn't affect the output of the CSS: https://play.tailwindcss.com/prkqHZsQ5U?file=config

@HydenLiu
Copy link
Author

As a work-around, you could have the values as strings and it shouldn't affect the output of the CSS: play.tailwindcss.com/prkqHZsQ5U?file=config

Yeah, thanks, I know that would fix it, but I think it's a bug and the numbers should be supported as well

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

No branches or pull requests

2 participants