I’m impressed by . The API is powerful and the implementation fast. It avoids unneeded rende…

  • The goal of this repo is to provide an implementation of the Animated library that is currently provided by React Native that can also be used by React in a web context.
  • At some point, React Native will itself depend on this library.
  • Additionally, it would be ideal if this library would be compatible with future potential “targets” of React where animation makes sense.
  • Right now the main export of this library is essentially just what is in the namespace in React Native, minus the , , and namespace.
  • Ideally, I’d like to make it so that , , and are exported, and just do the “right thing” depending on whether or not they are being used in the context of React Native or React Web.

animated – Declarative Animations Library for React and React Native

GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.

Declarative Animations Library for React and React Native

See the interactive docs.

The goal of this repo is to provide an implementation of the Animated library that is currently provided by React Native that can also be used by React in a web context. At some point, React Native will itself depend on this library.

Additionally, it would be ideal if this library would be compatible with future potential “targets” of React where animation makes sense.

namespace (explained below).

are exported, and just do the “right thing” depending on whether or not they are being used in the context of React Native or React Web. I’m not quite sure how we can do this yet without declaring dependencies on react native. Perhaps the platform specific file extensions can be used for this?

There are several parts of this library that need to have slightly different implementations for react-dom than for react-native. At the moment, I’ve just made these things “injectable” so that this library can stay dependent on only react.

Some of these I am implementing as “injectable”, even though right now it would technically work for both platforms. This doesn’t hurt anything, and attempts to make this library more compatible with future “targets” for react.

namespace, and include:

GitHub