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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@ginterdev/toolkit

v0.1.0-rc.12

Published

Complete toolkit for setting up a new project with a single command

Downloads

4

Readme

@ginterdev/toolkit

Fully-featured toolkit for my projects. Includes CLI for generating complete project boilerplate.

npm version

Installation

This library requires Node v12 or newer.

npm add --save-exact @ginterdev/toolkit

# or

yarn add --exact @ginterdev/toolkit

Usage

npx @ginterdev/toolkit [options]

Options

This CLI has some default features that will always be installed:

  • ESLint (with config),
  • Husky v4 (pre-commit hook),
  • lint-staged (with config),
  • Prettier (with config).
npx @ginterdev/toolkit

  # add Dockerfile and .dockerignore for building basic Node.js image
  --docker

  # install dependencies versions that don't support IE11 (like Tailwind v2)
  --drop-ie11

  # add 'jest' for testing
  --jest

  # add .github with workflow running basic checks (linters, type checking)
  --github-ci

  # specify exact node version to use for the project
  # notice, that <version> must be valid semver: <major>.<minor>.<patch>
  # when this option is not specified, default version will be used (12.20.1)
  --node <version>

  # use 'npm' instead of 'yarn' for commands
  --npm

  # add 'react' and 'react-dom' along with some basic components
  --react

  # add Next.js configuration
  # (notice that --react doesn't have to be specified because this option
  # indicates using of React)
  --nextjs

  # don't install dependencies as part of this CLI execution
  --skip-install

  # add Tailwind support
  # - creates config files
  # - add 'tailwindcss' as dependency
  --tailwind

  # add Typescript support
  --typescript

  # add simple .vscode directory with couple of settings
  --vscode

Example usage

Create project with Tailwind, Typescript and Next.js. Don't include Github Actions workflows or Docker support. Use Node v14.

npx @ginterdev/toolkit --node 14.15.4 --tailwind --nextjs --typescript