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

shmn-react-router

v0.0.9

Published

Basic implementation of a client side router for react with action and loader function!

Downloads

3

Readme

Dynamic JSON Badge

SHMN REACT ROUTER

  • basic implementation of a client side router for react
  • loader and action functions
  • automatically changes components rendered based on the current location
  • automatically runs appropriate loader function based on the route
  • automatically runs action functions based on the current route

Future Work

  • form component to automatically run action on form submit
  • error boundary elements
  • support for nested routes
  • run loaders that are independent of each other at the same time, preventing waterfall

Installation

npm i shmn-react-router

Example Project Showcasing All Features:

import { Route, Outlet, ClientLink, Router, useAction, useLoaderData, useNavigate } from "shmn-react-router"

// loader
function loadProfile() {
    return localStorage.getItem("username"); // this could be an api request instead
}

// action
function loginAction(formData: FormData): { result: boolean } {
    localStorage.setItem("username", formData.get("username") as string); // validate and send your form details
    return { result: true }; // if action was a success
}

function Profile() {
    const data = useLoaderData<ReturnType<typeof loadProfile>>();
    return (<>{data}</>);
}

function Login() {
    const submit = useAction<ReturnType<typeof loginAction>>();
    const navigate = useNavigate();
    const handleSubmit = (e: React.FormEvent<HTMLFormElement>) => {
        e.preventDefault();
        // you can choose to use the result of the action right after calling it
        const result = submit(new FormData(e.target as HTMLFormElement))
        if (!result) {
            console.warn("Could not submit form");
        } else {
            navigate("/");
        }
    }
    return (
        <form action="post" onSubmit={handleSubmit}>
            <input type="text" name="username" />
            <input type="submit" value="Login" />
        </form>
    );
}

function App() {
    const routes: Route[] = [
        {
            route: /^(\/profile|\/)$/, // regex for more expressive routes
            element: <Profile key={0} />,
            loader: loadProfile
        },
        {
            route: /^\/login$/,
            element: <Login key={1} />,
            action: loginAction
        }
    ]

    return (
        <div className="App">
            <Router routes={routes} >
                <nav>
                    <ClientLink to="/profile">Profile</ClientLink> {/* ClientLink is a plain anchor tag that won't cause a reload */}
                    <ClientLink to="/login">Logout</ClientLink>
                </nav>
                <Outlet /> {/* to render a matching route element */}
            </Router>
        </div>
    );
}

export default App;