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

@b.s/incremental

v2.1.10

Published

Simple universal composable async state management utilities

Downloads

34

Readme

Tests

About

Simple universal composable asynchronous state management utilities.

Features

  • CJS + ESM ✅
  • Lightweight ✅
  • Simple and easy to use ✅
  • Retry mechanism ✅
  • Caching ✅
  • Structural sharing ✅
  • Framework agnostic (note: BYO framework wrappers) ✅

Background

Managing asynchronous state is hard, on the backend the data access patterns we utilize varies wildly depending on the type of database we use and on the frontend we need to worry about keeping our data up to date, caching, network failures, and structural sharing to prevent rerenders.

incremental standardizes and simplifies the data access patterns we utilize on the backend and frontend by providing simple composable utilities allowing us to opt-in to the functionality we need.

The central idea is to utilize state-based CRDT's - a type of data structure which provides strong eventual consistency - to manage all data access, any changes to data are dispatched and applied by dispatch using onChange.

Usage

On the frontend, we often have to fetch data from the backend and then apply updates on a button click:

const user = createCRDT({
	initialValue: await service.getUserById,
	onChange: makeMonitor({
		fetchFn: service.putUser,
		onFetching: toggleLoadingIndicator,
		// For `fetchFn` to throw `onError`
		// `onError` has to throw
		onError: displayError,
	}),
});

const onSubmit = updates => user.dispatch(updates, { onChange: setUser });

or, sometimes we have incremental updates from multiple sources which need to be applied:

const chatMessages = createCRDT({
	initialValue: await service.getChatMessages(currentUser, recipient),
	onChange: makeMonitor({
		// makeRetry exponentially backs off
		fetchFn: makeRetry({
			retryFn: service.putChatMessage,
		}),
		onFetching: toggleLoadingIndicator,
	}),
});

const newMessagesSocket = new WebSocket(wsUri);
newMessagesSocket.onmessage = event =>
	dispatch(
		previousChat => {
			const message = JSON.parse(event.data);

			previousChat.messages.push(message.data);

			return previousChat;
		},
		// If `isPersisted`, then `chatMessages.onChange`
		// is not invoked
		{ isPersisted: true },
	);

const onSubmitChatMessage = newMessage =>
	chatMessages.dispatch(
		previousChat => void previousChat.messages.push(newMessage),
	);

More information in:

  • src/crdt/crdt.spec.ts
  • src/monitor/monitor.spec.ts
  • src/retry/retry.spec.ts

Contributions

  • Contributions are welcome, just make a pull request

"And I don't have a name, I don't have a name, no"