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

webtoolkit-utils

v0.7.3

Published

Typed utility toolkit for TypeScript projects with explicit entrypoints for browser, server, framework, database, and country modules.

Readme

webtoolkit-utils

Typed utility toolkit for TypeScript projects, split into explicit entrypoints by environment and domain.

Installation

npm install webtoolkit-utils

Install optional peers only when you use their entrypoints:

  • react for webtoolkit-utils/frameworks/react
  • mongoose for webtoolkit-utils/database/mongodb
  • sharp for webtoolkit-utils/server/media
  • express for richer webtoolkit-utils/server/http typings

Public Entrypoints

import { formatCurrency, resolveGeoPointCoordinates } from 'webtoolkit-utils'
import { shareContent } from 'webtoolkit-utils/browser'
import { isImageFile } from 'webtoolkit-utils/browser/files'
import { normalizeMongoose } from 'webtoolkit-utils/database/mongodb'
import { useDebounce } from 'webtoolkit-utils/frameworks/react'
import { wrapZodSchema } from 'webtoolkit-utils/frameworks/mantine'
import { generateRandomPassword } from 'webtoolkit-utils/server'
import { extractIpAddress } from 'webtoolkit-utils/server/http'
import { processImage } from 'webtoolkit-utils/server/media'

Notes

  • The root entrypoint only exposes environment-agnostic utilities.
  • The generic date and validation helpers use ISO-style inputs by default; localized parsing belongs in explicit modules.
  • Country-specific logic lives under countries/*.
  • Database-specific logic lives under database/*.
  • Framework-specific logic lives under frameworks/*.
  • Some domains are intentionally exposed only through their concrete subpaths, not through aggregate umbrella entrypoints.
  • Avoid deep imports from src/*; only the declared package exports are public.