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

@mdsfe/toolkit

v0.1.0

Published

A lightweight, modular TypeScript utility library for browser-friendly app development.

Readme

@mdsfe/toolkit

English | 简体中文

@mdsfe/toolkit is a lightweight, modular TypeScript utility library for browser-friendly app development. It borrows the practical layering ideas from epfe-utils, but removes business coupling so the package can be shared, published, and maintained as a public npm library.

Why Open Source

  • Build a reusable foundation instead of a one-off internal helper set
  • Lower adoption cost with clearer docs, stable exports, and public package metadata
  • Make external collaboration, issue tracking, and npm publishing straightforward
  • Keep business modules separate from general-purpose utilities

Features

  • Runtime dependency-free
  • TypeScript-first with generated declarations
  • Function-style APIs plus optional *Utils class facades
  • Tree-shakeable subpath exports
  • Safe in browser-first projects and import-friendly in non-browser environments

Modules

src/
  browser/     Query parsing, storage wrappers, runtime detection
  format/      Date, bytes, number, currency formatting
  function/    Debounce, throttle, memoize, retry, compose, pipe, curry
  object/      Deep clone, isEmpty, pick, omit
  string/      HTML escaping, keyword highlight, whitespace cleanup
  types/       Shared public type definitions
  validation/  Rule-based object validation helpers

Installation

npm install @mdsfe/toolkit

Quick Start

import {
  debounce,
  deepClone,
  formatDate,
  parseQuery,
  validate,
  required,
  email,
} from '@mdsfe/toolkit';

const profile = deepClone({
  name: 'Alice',
  email: '[email protected]',
});

const query = parseQuery('https://example.com?a=1&a=2&b=3');
const rules = [required('name'), email('email')];
const result = validate(profile, rules);

const log = debounce((value: string) => console.log(value), 200);

console.log(formatDate(Date.now(), 'YYYY-MM-DD HH:mm:ss'));
console.log(query, result.isValid);
log('toolkit');

Class-Style Usage

import {
  BrowserUtils,
  CommonUtils,
  FormatUtils,
  FunctionUtils,
  ValidationUtils,
} from '@mdsfe/toolkit';

const cloned = CommonUtils.deepClone({ id: 1 });
const date = FormatUtils.formatDate(Date.now(), 'YYYY-MM-DD');
const query = BrowserUtils.getUrlAllParams('https://example.com?a=1');
const handler = FunctionUtils.debounce(() => console.log('run'), 150);
const result = ValidationUtils.validate(
  { name: 'toolkit' },
  [ValidationUtils.required('name')]
);

console.log(cloned, date, query, result.isValid);
handler();

Subpath Imports

import { parseQuery } from '@mdsfe/toolkit/browser';
import { debounce, retry } from '@mdsfe/toolkit/function';
import { deepClone, isEmpty } from '@mdsfe/toolkit/object';
import { compactWhitespace, highlightKeyword } from '@mdsfe/toolkit/string';
import { formatBytes, formatCurrency } from '@mdsfe/toolkit/format';
import { validate, required } from '@mdsfe/toolkit/validation';

Compatibility Helpers

To ease migration from epfe-utils, toolkit keeps several familiar helpers with safer implementations:

  • getUrlAllParams
  • getUrlQuery
  • getSession
  • setSession
  • getUserOsInfo
  • isImageUrl
  • paddingZero

Development

npm install
npm run build
npm run typecheck
npm run release:check

Roadmap

  • Keep the public API small and stable
  • Add tests before wider npm distribution
  • Publish @mdsfe/toolkit to npm once the mdsfe scope publish permission is ready
  • Leave business-specific adapters outside this package

Open Source Docs