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

@frank3en/micro-library

v2.1.0

Published

feds share toys

Readme

micro-library

Contributor Covenant Codecov GitHub Workflow Status npm bundle size NPM

Front-end devs share toys.

Features

  • [x] Setup
  • [x] Lint
  • [x] Test -jest
  • [x] Babel - transpile code from cmj to esm vite
  • [x] Webpack - build - npm pack
  • [x] CI github actions
  • [x] Publish
  • [x] Semantic Release with Github Actions
  • [ ] Git hooks
  • [x] Test Coverage Report - in codecov

Getting started

Section1. Setup

  1. The Open Source Definition

  2. Code of Conduct there is something, [contact method], needs to be updated.

  3. npm-config-doc run npm config list -g

     init-author-email = "[email protected]"
     init-author-name = "xxx"
     init-license = "MIT"
     init-version = "0.0.1"

Section2. Lint

  1. ESLint
  2. eslint --init
  3. in package.json add script: lint: "eslint ."

Section3. Test

Section4. Babel

transpiling files && use esmodule to run test

babel config

in 03-trend-babel branch run npm run test, will occur:

Jest encountered an unexpected token

Solution:

npm install --save-dev @babel/core @babel/cli @babel/preset-env

create babel.config.json

add cross-env and {env:{test:{...}}} in babel.config.json

add eslint plugins for jest yarn add --dev eslint eslint-plugin-jest

Section5. Webpack for build command

The goal is to build src into a umd-lib.

  1. create webpack.config.babel.js
  2. add npm run build:umd script
  3. add prebuild script

Section6. CI with Github Actions

Section7. Publish

  1. npm login && npm publish
  2. dupication name -> add scope
    1. npm login --scope=<scope>
    2. change package name with <scope>/pagename
    3. npm publish --access public
  3. npm version

Section8. Semantic Release with Github Actions

  1. setup configuration
  2. add secrets
  3. update workflow

Other plugins like: semantic-release-gitmoji

TODOs...

  1. ui-components test & test, coverage
  2. lerna for monorepo
  3. package size
  4. document with storybook/dumi
  5. ...

Links

sections

open source libs

resources