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

next-router-components

v0.2.2

Published

react components built on top of the next-router

Downloads

17

Readme

Build Status

next-router-components

react components built on top of the next-router built on next-routes and the built-in next routing

motivation

  • Next js is very opinionated about routing.
  • After js wants you to roll your own routing.
  • next-routes is nice but doesn't give all of what we need
  • prefer using render props and component injection over HOC

getting started

Lets hook this into the routes configuration in routes.js

import Routes from "next-routes";
import { withRouteComponents } from "next-router-components";
const routes = new Routes();
routes
    .add("pagefoo", "/browse/:item?")

export default withRouteComponents(routes);

After this is configured just import the components and start routing!

import { Route, ToggableRouteLink } from "next-router-components"
// your react code will go here

components

Route

Props

{queryKey: string , to: string, component: React.ComponentType }

Example

import { Route } from "next-router-components"
const queryKey="item"; // this key is used to reference either
                       // A: a slug param defined in the next-routes route table. 
                       // B: a query string param.

const SomePage: React.SFC = () =>
    <>
        <Route queryKey={queryKey} to="pagefoo" component={PageFoo} />
        <Route queryKey={queryKey} to="pagebar" component={PageBar} />
        <Route queryKey={queryKey} to="pagequaz" component={PageQuaz} />
        <Route queryKey={queryKey} to="pagefi" component={PageFi} />
    </>;

TogglableRouteLink

Props

{queryKey: string , to: string, children(args: ToggleRouteArgs) => JSX.Element }

Example

import { TogglableRouteLink } from "next-router-components"

 <TogglableRouteLink
    queryKey={"item"}
    to={"new"}>
    {({ isSelected }) =>
         isSelected
         ? <div className="selected"> some data </div>
         : <div > some data </div>
    }
</TogglableRouteLink>