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

progress-lit

v0.1.2

Published

A controllable react progress bar. Useful for showing the progress of a client side route transition, e.g. when using Next.js (either `/pages` or `/app` router).

Downloads

3

Readme

progress-lit

A controllable react progress bar. Useful for showing the progress of a client side route transition, e.g. when using Next.js (either /pages or /app router).

Bundle size:

  • CommonJS: 2250 B (gzip: 1047 B, brotli: 906 B)
  • ESModule (modern): 1189 B (gzip: 556 B , brotli: 488 B)
  • ESModule: 2245 B (gzip: 1048 B , brotli: 912 B)

Requirements

  • React v17+
  • React DOM v17+

Installation

$ npm i progress-lit
# or
$ yarn add progress-lit

Examples

import * as React from 'react';
import { Progress, useProgress } from 'progress-lit';

// 1️⃣ Create a global progress instance, initialized lazily
let globalProgress: Progress | null = null;
function getGlobalProgress() {
	if (!globalProgress) {
		globalProgress = new Progress();
	}
	return globalProgress;
}

export function Example() {
	// 2️⃣ Subscribe to our global progress instance using the provided hook
	let state = useProgress(getGlobalProgress());

	return (
		<div>
			<h1>Basic example:</h1>
			{/* 3️⃣ Call methods on the global process class */}
			<button onClick={() => state.start()}>Start</button>
			<button onClick={() => state.done()}>Done</button>
			<button onClick={() => state.set(0)}>Set 0%</button>
			<button onClick={() => state.set(0.5)}>Set 50%</button>
			<button onClick={() => state.set(null)}>
				Set <code>null</code>
			</button>

			{/* 4️⃣ Subscribe to changes */}
			{state.status != null ? (
				<>
					<p>Progress: {Math.round(state.status * 100)}%</p>
					<progress value={state.status} />
				</>
			) : (
				<p>Progress: null</p>
			)}
		</div>
	);
}

Visit ./examples to view all usage examples.

Additional notes

  • In most cases, you want to keep the progress class outside the React tree so that you can call it's methods from anywhere.

  • In the basic example, the progress class is initialized lazily, so you can import it from anywhere without worrying about circular dependencies.

  • Use the useProgress hook to subscribe to changes in the global progress instance inside your React components. useProgress uses useSyncExternalStore under the hood.

Development

(1) Install dependencies

$ npm i
# or
$ yarn

(2) Run initial validation

$ ./Taskfile.sh validate

(3) Start developing by running the run_examples task. This spins up a development server hosting the different examples located in the ./examples folder on http://localhost:1234.

$ ./Taskfile run_examples

This project was set up by @jvdx/core