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

[@astrojs/tailwind] Cannot use custom animations defined by extending tailwind.config.cjs #5030

Closed
1 task
jChapman opened this issue Oct 9, 2022 · 4 comments
Labels
- P4: important Violate documented behavior or significantly impacts performance (priority)

Comments

@jChapman
Copy link

jChapman commented Oct 9, 2022

What version of astro are you using?

v1.4.6

Are you using an SSR adapter? If so, which one?

None

What package manager are you using?

npm

What operating system are you using?

Windows

Describe the Bug

When adding a new animation by extending the theme in tailwind.config.cjs as described in the tailwind documentation I am unable to get the example shown in the docs (wiggle) to work at all. Using the built in animations works just fine and the tailwind vs code plugin seems to find the new keyword and associated keyframes just fine. Copy pasting the same tailwind.config.cjs into the Tailwind Playground (and applying animate-wiggle to some element) shows it working just fine.

Recreated with the tailwind starter in gitpod before I read the issue template, I can recreate it in stackblitz if needed.

Link to Minimal Reproducible Example

https://gitpod.io#snapshot/41df471a-0ddf-4b48-b255-8d080df2aef5

Participation

  • I am willing to submit a pull request for this issue.
@jChapman
Copy link
Author

jChapman commented Oct 9, 2022

Only happens in preview, in the deployed site it works

@adrifer
Copy link

adrifer commented Oct 10, 2022

I have the same issue. Restarting npm run dev seems to do the trick.

It seems changes in the tailwind config file are just picked up when the server starts and not just when saving the config file.

It seems it's being fixed and tracked here #4913

@matthewp
Copy link
Contributor

That's right, currently you have to restart the server on Tailwind config changes. #4947 will fix that.

@matthewp matthewp added the - P4: important Violate documented behavior or significantly impacts performance (priority) label Oct 10, 2022
@bluwy
Copy link
Member

bluwy commented Oct 17, 2022

Closing as #4947 is merged.

@bluwy bluwy closed this as completed Oct 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
- P4: important Violate documented behavior or significantly impacts performance (priority)
Projects
None yet
Development

No branches or pull requests

4 participants