Pkg
Stats

npm package discovery and stats viewer.

Discover Tips

General search
[free text search, go nuts!]
Package details
pkg:[package-name]
User packages
@[username]

Sponsor

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.

Twitter
@PkgStats
GitHub
pkgstats
Twitter
@ryanhefner
GitHub
ryanhefner
Site
ryanhefner.com

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 🙏

Framework
react / react-dom
Server
next / express / next-routes
Data Store
redux / react-redux / next-redux-wrapper / redux-thunk / redux-logger
Caching
lru-cache
CSS / Styling
next-page-transitions / styled-components
Typeface
@ibm/plex
Avatars
gravatar
Data Viz
chart.js / react-sparklines
Date formatting
dayjs
Infinite scrolling
react-scroll-trigger
Markdown rendering
react-markdown
Repository url parsing
hosted-git-info
User data
npm-user
Compiling
babel-plugin-module-resolver / babel-plugin-styled-components
Types
prop-types
Odds & Ends
es6-promise / isomorphic-fetch

© 2026 – Pkg Stats / Ryan Hefner

@miniest/mini-common

v0.0.15

Published

4 years ago

Common tools for miniest people.

0High
0Medium
0Low

mini-common-js

Common tools for miniest people.

Server

If you want to use Server module you must manually include express into your dependencies. It is intentionally not listed in peerDependencies because not every user of mini-common is interested in the Server module.

MiniError

Error class with specified http status code. By default returns 500. For other types of error see the classes extended from MiniError.

AuthorizationError

Error extended from MiniError, should be used with unauthorized access/unauthenticated user cases. Its http status code is 401.

ForbiddenError

Error extended from MiniError, should be used in case of missing permissions. Its http status code is 403.

Development

Commit message

We follow conventional changelog patter for commit messages.

See [https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-changelog-angular].

We preffer these prefixes:

feat: new feature added (will be seen in changelog)
fix: fix of existing code (will be seen in changelog)
perf: changed performance of some code (will be seen in changelog)
build: build system and ci related stuff (not seen in changelog)
docs: documentation related stuff (not seen in changelog)
test: tests related stuff (not seen in changelog)

If you cannot determine correct prefix for your change simple do commit without a prefix. Try to use feat/fix/perf prefixes for any user related stuff to let enduser know about the change.