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-routing-tools

v1.1.0

Published

Easy dynamic routing, with first-class typescript support.

Downloads

11

Readme

Next routing tools!

Easy dynamic routing, with first-class typescript support.

Define routes

You have to define all possible routes in advance. The first argument of the route is the path (as seen in the browser). The second argument is the page (relative from the /pages directory) that should be rendered in Next.

import { route } from 'next-routing-tools'

const routes = {
    index: route('/'),
    about: route('/about'),
    blog: route('/blog'),
    blogPost: route('/blog/:slug', '/blog-single')
}

Server-side

Import the routes and the handler (in this case for express). Then let the handler take on all requests.

If you want to do some more custom things before rendering, you can do so by just using the values from a route.

import { handle } from 'next-routing-tools/express'
import { routes } from './routes'

const server = express()
const app = next()

app.prepare().then(() => {
    // let the routes be handled automatically
    server.get('*', handle(routes, app))

    // Or, if you want to do more than just render you can use this.
    server.get(routes.blogPost.path, (req, res) => {
        // do more stuff here
        app.render(req, res, routes.blogPost.page, { slug: req.params.slug })
    })
})

Client-side

On the client side you have to first set up the RouteProvider. This will make sure all Link components have access to the routes available in this app.

You can then use the Link component and provide an href which includes the params (and optionally query params).

I'm still figuring out what's the best approach for also providing routes as objects, or just parameters as object. If you have any ideas for this API, please create an issue and I can take a look.

import { RouteProvider } from 'next-routing-tools'

// Provide routes
<RouteProvider routes={routes}>
    <Component {...props} />
</RouteProvider>

-- 

import { Link } from 'next-routing-tools'

// Then somewhere in your app use
<Link href='/blog/fooo' />
<Link href='/blog/fooo?something=true' />

Heavily inspired by next-routes (thanks!). But as I was using typescript I wanted a slightly different api.

Development

  • Install dependencies: npm i
  • Run tests: npm run test
  • Run build: npm run build
  • Run example: npm run example