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

pure-redux-router-link

v1.0.14

Published

a simple but effective <Link /> component for pure-redux-router (better for SEO rather than dispatching yourself)

Downloads

11

Readme

pure-redux-router-link

A simple but effective <Link /> component for pure-redux-router (better for SEO rather than dispatching yourself)

Installation

yarn add pure-redux-router-link

Usage

import Link from 'pure-redux-router-link'

// as a standard href path string:
<Link href='/list/db-graphql'>DB & GRAPHQL</Link>

// as an array of path segments:
<Link href={['list', 'react-redux']}>REACT & REDUX</Link>

// as an action object:
<Link href={{ type: 'LIST', payload: { category: 'fp' } }}>FP</Link>

In all 3 cases, a simple link will be rendered, eg:

<a href='/list/fp'>FP</a>

Recommendation

Creating your links with hrefs as an action object is obviously the best solution, as it will allow you to change static path segments in the routesMap you pass to connectRoutes() at any time, without having to change any of your <Link /> components. That means you only have to change URLs in one place.

For example, if you have:

import { createStore, compose, applyMiddleware, combineReducers } from 'redux'
import createBrowserHistory from 'history/createBrowserHistory'
import connectRoutes from 'pure-redux-router'

const history = createBrowserHistory()

const { enhancer, middleware, reducer } = connectRoutes(history, {
  LIST: '/list/:category'
})

const rootReducer = combineReducers({ location: reducer })
const store = createStore(rootReducer, compose(enhancer, applyMiddleware(middleware)))

Then you can change the static segment of the path at any time, eg:

const { middleware, enhancer, reducer } = connectRoutes(history, {
  LIST: '/browse/:category'
})

But its entirely up to you. If it's easier to start to thinking in terms of paths, go for it! If that's the case, we recommend the array syntax, since its easier to pass variables, eg:

const category = 'react-redux'
const href = ['list', category]
<Link href={href}>REACT & REDUX</Link>

vs

const category = 'react-redux'
const href = `/list/${category}` // can get long & yucky with lots of variables
<Link href={href}>REACT & REDUX</Link>

Additional Props:

  • down: boolean = false - if true supplied, will trigger linking/dispatching onMouseDown instead of onMouseUp
  • shouldDispatch: boolean = true - if false will not dispatch (useful for SEO when action handled elsewhere)
  • target: string - eg: '_blank' to open up URL in a new tab (same as standard target attribute to <a> tags)
  • onPress: (SyntheticEvent) => ?boolean - you can provide an onPress handler to do anything you want (e.g. play a sound), but if you return false it will prevent linking/dispatching just as you may be used to. TIP: Use returning false instead of shouldDispatch when you want to dynamically determine whether to trigger the action or not!
  • ...props: - you can pass any additional props that an <a> tag takes, such as className