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

@tjmonsi/small-router

v0.0.3

Published

small-router

Downloads

6

Readme

@tjmonsi/small-router pipeline statuscoverage report

small-router

Page Documentation can be found at: https://tjmonsi.gitlab.io//small-router/

This webcomponent follows the open-wc recommendation.

Installation

npm i small-router

Usage

Load the module, then get the element via querySelector.

Add a routes object, which is a data dictionary object where the keys are routes and the values are objects with 4 properties:

  • render: this is the html that you want to render when the particular route has been matched to the url.
  • load: this can be a function or a promise or an array of functions or promises that will be called AFTER the render has been done. Take note that the ordering will be followed, but the promises are done almost simultaneously (they are not dependent on each other). If one promise fails, it will all fail.
  • preloadChecks: this can be a function or a promise or an array of functions or promises that will be called BEFORE the render will be done. This can be used to check for authorization for a page. ake note that the ordering will be followed, but the promises are done almost simultaneously (they are not dependent on each other). If one promise fails, it will all fail. If it fails, it will go back to the fallbackUrl. If the function returns true, it will also fail.
  • fallbackUrl: the path that it will go to if the preloadChecks returns an error or returns true.

There is a special route called not-found, which can be a fallback for 404 not found.

<small-router></small-router>

<script type="module">
  import 'small-router/small-router.js';

  const router = document.querySelector('small-router');
  router.routes = {
    '/demo': {
      render: () => html`Hello <a href="./demo1">world</a> - <a href="/demo2">haha</a>`
    },
    '/demo1': {
      render: () => html`<test-component></test-component>`,
      load: async () => import('./test-component.js'),
      fallbackUrl: '/demo'
    },
    '/demo2': {
      preloadChecks: () => 'some error',
      fallbackUrl: '/demo1'
    }
  };

  router.addEventListener('route-change-error', function ({ detail }) {
    console.log('error when changing routes', detail);
  });
</script>

Linting and formatting

To scan the project for linting and formatting errors, run

npm run lint

To automatically fix linting and formatting errors, run

npm run format

Testing with Web Test Runner

To execute a single test run:

npm run test

To run the tests in interactive watch mode run:

npm run test:watch

Demoing with Storybook

To run a local instance of Storybook for your component, run

npm run storybook

To build a production version of Storybook, run

npm run storybook:build

Tooling configs

For most of the tools, the configuration is in the package.json to minimize the amount of files in your project.

If you customize the configuration a lot, you can consider moving them to individual files.

Local Demo with web-dev-server

npm start

To run a local development server that serves the basic demo located in demo/index.html

Installation

You should have the following:

  • Node version 12 or 14

To install run,

npm install

Usage

To run this project

npm start

Documentation

Please visit the repo page or if you want to build your own copy here, you have to install Hugo globally

brew install hugo

Then run the following commands:

npm run serve:docs

If you want to just build the docs,

npm run build:docs