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

bounce-in-style

v0.0.40

Published

The Bounce style guide, formatter, and commit validator.

Readme

Bounce in Style

Version npm License

The Bounce style guide, formatter, and commit validator.

Goal

  • Single source of truth for all linting, formatting, commit message validation, changelog generator, semantic versioning
  • Minimal config
  • Compatible with all Bounce Typescript projects (Express, React, React Native)

Install

  • Remove any installations of ESLint or Prettier & all associated config files (keep your .eslintignore and .prettierignore files)
  • Install with npm
# npm
npm install bounce-in-style -D

# yarn
yarn add bounce-in-style -D

Usage

Git/Husky hook (recommended)

  • Fresh install of Husky (version 6 has some major changes, ensure to remove existing Husky installations prior to starting)
npm uninstall husky
npm install husky -D
npx husky install
  • Add this "prepare" script to package.json so that husky gets setup on npm install:
{
  "scripts": {
    "prepare": "husky install"
  }
}
  • Add git hook with Husky

Lint and format

# react projects
npx husky add .husky/pre-commit "npx bis --staged --react"

# react-native projects
npx husky add .husky/pre-commit "npx bis --staged --react-native"

# all other projects (ie backend)
npx husky add .husky/pre-commit "npx bis --staged"

Commit validation

 npx husky add .husky/commit-msg "npx commitlint --edit \"\$1\" --config ./node_modules/commitlint-config-bouncedinc/index.js"

CLI

# with npm
npx bis -h

# Usage
#   $ npx bis [flags]

#   Options
#   --help               Print help message.
#   -r, --react          Use for React projects.
#   -n, --react-native   Use for React Native projects.
#   -s, --staged         Only run on staged files. Useful when adding as a git hook.
#   -c, --check          Only check files. Skips running Prettier and doesn't use the --fix flag for ESLint.
#                        This option does not support the --staged flag.

Bounce project recommendations

VSCode

To add linting capabilities to VSCode

  • copy the .vscode folder at the root of your project
  • (if using React) replace the configFile path with ./node_modules/eslint-config-bouncedinc-react/index.js
  • (if using React Native) replace the configFile path with ./node_modules/eslint-config-bouncedinc-react-native/index.js

Running tsc

All Bounce projects should have a git hook (either pre-commit or pre-push) for running tsc.

Extending ESLint config

We don't recommend extending the config when using internal to Bounce, instead a PR should be made into this repo to add the change for everyone. If you do need to extend the config, you can treat it like any other eslint config. The simplest way to do so can be seen in the .eslintrc file at the root of this repo.

What's next