-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Eliminate dependency on Velocity #4441
Comments
@zenweasel Does it make sense to try CSS animations or is jQuery fine? |
@dancastellon No jQuery ever. |
Animating with Javascript is fine though, I created this ticket because I don't think the type of animations we're performing warrant an animation library. Honestly this is not a high priority if it turns out to be a tough task. |
aldeed
added a commit
that referenced
this issue
Aug 23, 2018
…-eliminate-velocity #4441: Improve animations and dynamically import animation libraries to reduce bundle size
spencern
added a commit
that referenced
this issue
Aug 31, 2018
This was referenced Aug 31, 2018
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue Description
We currently have a dependency on
Velocity
for animating parts of our client application.Velocity is a DOM animation library which makes doing some complex animations performant and simple.
We currently use velocity to do one of two things.
Neither of these animations should need a library to do well or simply and don't justify the added overhead of 94.5kb
The animations using velocity are contained in one of 6 files
This issue is to eliminate the dependency on Velocity and replace any animations that are using Velocity with another method of animation.
The text was updated successfully, but these errors were encountered: