-
Notifications
You must be signed in to change notification settings - Fork 671
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
@emotion/core keyframes missing scope after update #1814
Comments
Hey @hoffination 👋 Thanks for the issue! Could you send me your lockfile? (package-lock.json or yarn.lock) A workaround I see is calling that |
I think you'd need to try 0.4-alpha, actually. We bumped to 0.5 because of Emotion version update. Meanwhile — does animation: `0.5s ${keyframe}` syntax work for you? |
Oh yeah!
totally fixes it for me! I had some other usages though that broke initially until I took the
|
I ran into this as well, using:
Can confirm that doing... animation: `0.5s ${animation}` Fixes it I wonder if the "object syntax" example should be removed/changed on this page? https://theme-ui.com/guides/keyframes#usage |
Excellent callout @TranquilMarmot! Just made a PR updating that page. |
🚀 Issue was released in |
🚀 Issue was released in |
Describe the bug
Getting
TypeError: Cannot read property 'name' of undefined
when running a keyframe againsttheme-ui
9.1.0
Error is coming from
this.name
referenced inside thetoString
function:To Reproduce
For starters I'm updating from
0.3.1
so I'm a bit worried I've missed a step along the way...First I'm defining a keyframe and using it inside my component like so:
Code example
I do this in a few places in the app and it only errors when the keyframe is triggered. I've omitted some details to make the usage a bit clearer.
Expected behavior
Previous functionality is that the styles get applied as expected without throwing a runtime error.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
I'll post some my dependencies here. Not sure how much they'll help but maybe something will jump out at ya:
`package.json`
The text was updated successfully, but these errors were encountered: