npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

react-transition-router

v1.1.8

Published

* Animations made with [velocity-react](https://github.com/google-fabric/velocity-react) * Extends [history](https://github.com/ReactTraining/history) for directional animations

Downloads

54

Readme

A router for React with lifecycle hooks and animations


Route

Props

  • path: PropTypes.string.isRequired
  • component: PropTypes.object.isRequired
  • exact: PropTypes.bool
  • append: PropTypes.bool
  • absolute: PropTypes.bool
  • animations: PropTypes.object

path: REQUIRED

A unique path that determines the URL to a component

component: REQUIRED

The element that will be available at the path. Should be an instance of the component you want to render.

exact

If exact is set to true, the exact url given as a prop must be entered into the address bar in order to get to that page. If exact is set to false, then if the url in the address bar matches the url given as a prop and then some, then the page that is closest to the url in the address bar will be given.

For example, if the path prop is set to /example/ and the exact prop is set to true, you can only get to the /example/ page by inputting http://www.domain.com/example or http://www.domain.com/example/. However, if the exact prop is set to false with that same url, you could get to the example page by going to http://www.domain.com/example/hello/world. In this scenario, /hello/world would be passed to the component function in a data object (it is a member variable of the object accessible by dataObject.urlParams) so that the page can handle any extra stuff it needs to do with the url data.

An example of what the above is describing would look something like this:

<Route path="/example/" key="test" component={dataObject => <Test parameters={dataObject} state={appState} />} />

Where the rest of the url would be accessible from dataObject.urlParams.

append

If you would like to append pages/elements (i.e. a modal), you can do that by adding the append prop to a route you would like to append. This will only work if the parent page and the page to be appended is an 'approximate' route.

absolute

Helpful for when animations are not serialized. Prevents elements transitioning from affecting each other's place on the page. Adds position: 'absolute' and top:0, bottom:0, left:0, right:0 to the routes. Defaults to false.

animations

Specific animations for a particular page. This will override any generic animations provided to the PageTransition. See animations in PageTransition for more details on how to format the animations.


PageTransition

Props

  • routes: PropTypes.array.isRequired
  • fallback: PropTypes.string
  • routeWillChange: PropTypes.func
  • routeDidChange: PropTypes.func
  • exitAnimationBegin: PropTypes.func
  • exitAnimationFinish: PropTypes.func
  • enterAnimationBegin: PropTypes.func
  • enterAnimationFinish: PropTypes.func
  • loadAnimationName: PropTypes.string
  • serialize: PropTypes.bool
  • animations: PropTypes.object

routes: REQUIRED

List of Route items

fallback

Path to a Route that will be displayed if no other page is found. Equivalent to a 404 error page. Does not matter if it is exact or not.

routeWillChange

Callback function triggered before the route changes to a different page

routeDidChange

Callback function triggered after a route changed to a different page (after all animations have completed)

exitAnimationBegin

Callback function triggered when the animation of the leaving page begins

exitAnimationFinish

Callback function triggered when the animation of the leaving page completes

enterAnimationBegin

Callback function triggered when the animation of the entering page begins

enterAnimationFinish

Callback function triggered when the animation of the entering page completes

loadAnimationName

The name of the animation that should occur on page load. See animations for an example.

serialize

Boolean determining whether or not the animations should chain one after the other, or happen concurrently. Defaults to true so animations will chain.

animations

An object defining the animations that should happen. Every animation object should have a push and a pop key, which each should contain a enter and exit key. push events occur when either a new route was pushed to the history, or when the forward button in the browser is clicked. pop events occur when the back button in the browser is clicked. The enter animation refers to the page entering the screen, and the exit animation refers to the page exiting.

Each animation should be formatted via the Velocity documentation. All of these animations are placed into Velocity's VelocityTransitionGroup.

Example:

const animationObject = {
  load: { animation: { opacity: [1, 0], translateY: ['0%', '100%'] }, duration: 600 },
  pop: {
    enter: { animation: { opacity: [1, 0], translateX: ['0%', '100%'] }, duration: 500 },
    exit: { animation: { opacity: [0, 1], translateX: ['-100%', '0%'] }, duration: 500 },
  },
  push: {
    enter: { animation: { opacity: [1, 0], translateX: ['0%', '-100%'] }, duration: 500 },
    exit: { animation: { opacity: [0, 1], translateX: ['100%', '0%'] }, duration: 500 },
  },
};

Example Usage

import React from 'react';
import AppState from './state/AppState';
import { PageTransition, Route } from 'react-transition-router';
// import pages
import Home from './pages/Home';
import Test from './pages/Test';

// create global state
const appState = new AppState();

export default class Routes extends React.Component {
  constructor(props) {
    super(props);

    const animationObject = {
      load: { animation: { opacity: [1, 0], translateY: ['0%', '100%'] }, duration: 500 },
      pop: {
        enter: { animation: { opacity: [1, 0], translateX: ['0%', '100%'] }, duration: 500 },
        exit: { animation: { opacity: [0, 1], translateX: ['-100%', '0%'] }, duration: 500 },
      },
      push: {
        enter: { animation: { opacity: [1, 0], translateX: ['0%', '-100%'] }, duration: 500 },
        exit: { animation: { opacity: [0, 1], translateX: ['100%', '0%'] }, duration: 500 },
      },
    };

    this.state = {
      routes: [
        <Route path="/" key="Home" component={<Home state={appState} />} animations={animationObject} />,
        <Route exact path="/test" key="Test" component={ <Test state={appState} />} />,
      ],
    };
  }

  render() {
    const animationObject = {
      load: { animation: { opacity: [1, 0], translateY: ['0%', '100%'] }, duration: 600 },
      pop: {
        enter: { animation: { opacity: [1, 0], translateX: ['0%', '100%'] }, duration: 500 },
        exit: { animation: { opacity: [0, 1], translateX: ['-100%', '0%'] }, duration: 500 },
      },
      push: {
        enter: { animation: { opacity: [1, 0], translateX: ['0%', '-100%'] }, duration: 500 },
        exit: { animation: { opacity: [0, 1], translateX: ['100%', '0%'] }, duration: 500 },
      },
    };

    return (
      <div id="app-container">
        <PageTransition
          routes={this.state.routes}
          animations={animationObject}
          loadAnimationName="load"
        />
      </div>
    );
  }
}

History

How to push and pop the state

import { History } from 'react-transition-router'

  • listen(location, direction)
  • unlisten(id)
  • push(path)
  • pop()
  • allowPushDuplicates: boolean

listen(callback)

Takes a callback function as a parameter that will be called every time the history is modified with the push or pop command, and returns a unique identifier that can be used to later remove the callback if necessary. The callback will be passed two parameters: the path being pushed, as well as the direction the history is going (PUSH or POP).

unlisten(id)

Takes the unique identifier string returned by the listen function and unregisters the callback function so it no longer receives callback notifications

push(path)

Pushes a new path to the history. This event will trigger the callback function passed into listen.

pop()

Pops a path from the history. This event will trigger the callback function passed into listen.

allowPushDuplicates

Defaults to false so the current path cannot be pushed again. If set to true, it allows the current path to be pushed to the history again.


Example Usage

import { History } from 'react-transition-router';

History.listen((location, direction) => {
  console.log(`History changed to: ${location}, via ${direction}`);
});

History.push('/test');
History.pop();