Fire a callback after a transition or immediately if the browser does not support transitions
A react component toolset for managing animations
Animated transitions for D3 selections.
TypeScript definitions for react-transition-group
TypeScript definitions for d3-transition
Zero dependency React transition state machine.
listen for entering/leaving inside nested transitions
Reactive primitives for implementing transition effects in SolidJS
Hyphenates a camelcased CSS property name
The code in this package has moved. We recommend you to use `CSSTransitionGroup` from [`react-transition-group`](https://github.com/reactjs/react-transition-group) instead.
Components to manage animations for SolidJS
☄️ An extremely light-weight react transition animation hook which is simpler and easier to use than react-transition-group
A fork of styled-components that supports concurrent rendering
transition-group ui component for preact
Define transition animation for entering and leaving
React Native bindings for Lottie
XState for finite state machines
Easily add animated transitions between pages using Next.js App Router.
Common transition components for Chakra UI
The code in this package has moved. We recommend you to use `TransitionGroup` from [`react-transition-group`](https://github.com/reactjs/react-transition-group) instead.
Animation Variables and Mixins used by Material Components for the web
A React component to animate replacing one element with another.
Custom Vue transition to collapse elements horizontally or vertically. Works with both fixed and 'auto' width or height.
☄️ An extremely light-weight react transition animation hook which is simpler and easier to use than react-transition-group
exposes state machine method to run code after a transition is committed to the database
Automated JIRA issues transitions after deployment with Capistrano
ActiveRecord aware workflow (state machine) module that will also work with any plain old ruby object.
A Rack middleware to make URLs in one-page webapps easier. In a couple of recent projects, I've needed to avoid full page refreshes as much as possible. In the first, I wanted to keep an embedded music player active while the user was browsing. In the second, I just wanted fancier transitions between pages. It's possible to do this in an ad-hoc way, but I very quickly got tired of hacking things together. Enter Onesie. Onesie congealed from these requirements: * I want a one-page web app, * But I want the back button to work, * And I want search engines to still index some stuff, * And I (mostly) don't want to change the way I write a Rails/Sinatra app. If someone visits <tt>http://example.org/meta/contact</tt>, I want them to be redirected to <tt>http://example.org/blah/#/meta/contact</tt>, but after the redirection I still want the original route to be rendered for search engine indexing, etc. When Onesie gets a request, it looks to see if under your preferred one-page app path ("blah" in the example above). If it's not, Onesie sets the current request's path in the session and redirects to your app path. If a request is under the one-page app path, the "real" request's path is retrieved from the session and used for subsequent routing and rendering. This means that, as above, a request for http://example.org/meta/contact Will be redirected to http://example.org/blah/#/meta/contact But still render the correct action in the wrapped app, even though URL fragments aren't passed to the server. This is a terrible explanation. I'll write a sample app or something soon.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.