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

@standardbeagle/virtual-router

v1.0.1

Published

Compoent router is a basic memory only hook based router for react. Component router does not interface or connect with the browser path at all.

Downloads

3

Readme

Component Router

Compoent router is a basic memory only hook based router for react. Component router does not interface or connect with the browser path at all.

Why Component Router

I built component router because I was working on a complicated react component intented to be used by multiple projects. I initally started building it with react router, which worked exactly as I needed it in my test project. However when I included it in multiple external projects, it forced me to use react router as the router for the entire project, and copy all the component routes up to the main router file.

I'm a huge fan of using routing for UI state management. I think the process of tying rednering components to manipulating the path with links and pattern matching makes my applications easier to maintain and understand. It also happens to be the way that http servers manage loading files.

Getting Started

npm i @standardbeagle/component-router

The core of your application is the Provider which manages and shares path and route data to all its child components.

  <Component>