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

typescript-safe-router

v1.0.2

Published

A type-safe router for TypeScript

Downloads

14

Readme

typescript-safe-router

A type-safe router for TypeScript. Read the WHY and HOW in this blog post: https://frigoeu.github.io/typescriptsaferouter.html

Typescript-safe-router is tiny (1kb minified/gzipped), framework-independent and fully type-safe! Make, change and use routes without worrying if you're keeping everything synchronized.

Usage

import {makeRoute, makeRouter} from "typescript-safe-router";

const employeeRoute = makeRoute("employee", {employeeId: "number"});

// Building URL's
employeeRoute.buildUrl({employeeId: 5}); // "#/employee/employeeid/5"

// Matching URL's
employeeRoute.matchUrl("#/employee/employeeid/5") // {employeeId: 5}
employeeRoute.matchUrl("#/employee/employeeid/test") // null

// Building a full router
export const messages = makeRoute("messages", {startDate: "date"});
export const employees = makeRoute("employees", {employeeId: "number"});

makeRouter(
  messages, (opts) => {
    console.log("We've navigated to the messages page! The startDate is in year: " + opts.startDate.getFullYear().toString())
    return null;
  }).registerRoute(
  employees, (opts) => {
    console.log("We've navigated to the employees page! Employee number: " + opts.employeeId.toString())
    return null;
  });

Type definition syntax

The following strings can be used to define the types of your route parameters:

"string"
"string | null"
"date"
"date | null"
"number"
"number | null"
"boolean"
"boolean | null"

A full example with React

import * as Messages from "./messages";
import * as Employees from "./employee";
import * as React from "react";
import {makeRoute, makeRouter, Router} from "./router";

// Defining what routes we have, and what parameters the urls contain
export const messages = makeRoute("messages", {startDate: "date"});
export const employees = makeRoute("employees", {employeeId: "number"});

class App extends React.Component<{}, {}> {
  private router: Router<JSX.Element>;

  constructor(props: {}) {
    super(props);

    // Defining what we want functions we want router.match to execute for every route
    this.router = makeRouter(
      messages, ({startDate: Date}) => <Message.Page startDate={startDate} />).registerRoute(
      employees, ({employeeId: number}) => <Employees.Page employeeId={employeeId} />);    

    window.onhashchange = () => this.forceUpdate();
  }

  startPage(): JSX.Element {
    return <div>You have arrived at the start page</div>;
  }

  render() {
    let fromRouter = this.router.match(window.location.hash);
    return (fromRouter === null) ? this.startPage() : fromRouter;
  }
}