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

@threepointone/react-router-modules

v1.0.2

Published

react-router-modules ---

Downloads

6

Readme

react-router-modules

[work in progress]

to prpl and beyond

usage

npm install @threepointone/react-router-modules

add @threepointone/react-router-modules/babel to your babel plugins

the big idea

we make a single change to the <Route/> api

// this 
import User from './user.js'
// ...
<Route path='/user/:id'
  component={User}
/>

// becomes this 
// ...
<Route path='/user/:id'
  module='./user.js'
/>
  • no new imports/apis
  • renders default export by default
  • handles code splitting, SSR, behind the scenes
  • works with render, children props as expected
<Route path='/user/:id'
  module='./user.js'
  render={ ({ Module }) => Module ? 
    <Module.default /> : 
    <span>loading...</span> )}
/>
// or use children-func, to render even when path doesn't match
  • todo - preserve server side rendered html while module asyncly loads
<Route path='/user/:id'
  module='./user.js'
  preserve />
// this will render SSR, but split code out and load separately
// server side rendered html will stay till module loads(!)
  • todo - statically extract mapping of url -> modules
matchModule('/user/213', { Module } => {
  // and then fetch data, render <App />, whatever you like 
})

// you can now expose this via an api endpoint. and handle data fetching, etc 
// this can also get treeshaked out lol
  • use in tandem with your server for PRPL
// TODO

constraints -

  • path has to be a static string

todo -

  • auto endpoints for data fetching
  • prefetch links
  • <Html/>
  • service workers
  • all that jazz