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 🙏

© 2026 – Pkg Stats / Ryan Hefner

use-state-log-value

v0.2.0

Published

State change logging utilities for frontend and backend

Readme

use-state-log-value

State logging for React with a clean one-line hook API, plus optional backend server utilities.

Features

  • Per-component state logging: createUseState('ComponentName') returns a useState-like hook that logs with that component name
  • Global logger config: setLogServer('offline') or setLogServer('https://...')
  • offline mode (dev only): sends logs to local stateLogServer
  • Generated local CLI binary: ./node_modules/.bin/stateLogServer
  • Local server writes logs to ./.log-values/ with daily rotation (backend-YYYY-MM-DD.log)
  • Backend API: POST /ingest, GET /states
  • Backend helper exports: startServer(port), setUpNotification(...)
  • Optional Telegram notification for error logs
  • Jest tests + frontend demo + Cypress video flow
  • Cursor rule: on install, a rule file is copied to your project’s .cursor/rules/ so Cursor can use the library correctly. If you use --ignore-scripts or the rule wasn’t installed, run: npx use-state-log-value-install-rules

Install

npm install use-state-log-value

Frontend usage

Create a hook per component so logs are tagged with the correct component name:

import { createUseState, setLogServer } from 'use-state-log-value';

setLogServer('offline');
// or
setLogServer('https://some-remote-server.com');

const useStateLogValue = createUseState('Filters');
function Filters() {
  const [type, setType] = useStateLogValue<'all' | 'movie' | 'tv'>('all', 'imdb-filter');
  const [query, setQuery] = useStateLogValue('', 'search-query');

  return (
    <>
      <button onClick={() => setType('movie')}>Movie</button>
      <button onClick={() => setType('tv')}>TV Series</button>
      <input value={query} onChange={(e) => setQuery(e.target.value)} />
    </>
  );
}

Offline mode local server

setLogServer('offline') is active only when NODE_ENV=development.

Start the local server:

./node_modules/.bin/stateLogServer
# or
npx stateLogServer
# optional
npx stateLogServer --port 8787
# help
npx stateLogServer --help

This writes logs to:

  • ./.log-values/backend-YYYY-MM-DD.log

Environment variables

  • STATE_LOG_SERVER_PORT: default local server port if --port is not provided
  • STATE_LOG_READ_DAYS: number of rotated log days scanned by GET /states (default: 3)

Backend usage

import { startServer, setUpNotification } from 'use-state-log-value/backend';

startServer(3000);

setUpNotification({
  telegramBotToken: '...',
  groupId: -1001234567890,
  topicId: 3,
});

Test

npm test
npm run test:frontend
npm run test:backend

Examples

npm run example:frontend
npm run example:backend

Cypress E2E

npm run example:frontend
npm run cypress:run