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

@bancame/eslint-config

v1.1.4

Published

ESLint configuration for Bancame projects using TypeScript and React

Downloads

15

Readme

Bancame ESLint Flat Configuration

A batteries-included, flat-config ESLint setup for TypeScript & React projects, built on top of ESLint v9. It ships with sensible defaults and plugins to cover:

  • TypeScript (@typescript-eslint/parser, @typescript-eslint/eslint-plugin)
  • React/JSX (eslint-plugin-react, eslint-plugin-react-hooks, eslint-plugin-react-refresh)
  • Import ordering (eslint-plugin-import)
  • Google Translate helper rules (eslint-plugin-react-google-translate)
  • Prettier integration (eslint-config-prettier)

⚠️ Uses ESLint’s new flat config format. If you prefer classic .eslintrc.js, see the “Legacy Usage” section below.


Table of Contents


Installation

  1. Install the package and required peers
npm install --save-dev @bancame/eslint-config
  1. Install ESLint and required plugins
npm install --save-dev eslint-import-resolver-typescript

If you use React, also install the React plugins:

npm install --save-dev eslint-plugin-react-hooks

Basic Usage (flat config)

  1. Create a eslint.config.mjs file in your project root:
import { defineConfig } from 'eslint/config';
import baseConfig from '@bancame/eslint-config';

export default defineConfig(baseConfig);
  1. (Optional) Create an .eslintignore file to exclude files/folders from linting, e.g.:
build/
dist/
node_modules/
  1. Run ESLint:
npx eslint . --ext .js,.ts,.jsx,.tsx

Optional: React support

  • The config scopes React-specific rules only to .jsx/.tsx files.
  • In a non-React repo you may omit installing the React plugins; ESLint will skip those rules automatically.

Legacy Usage (.eslintrc.cjs)

If you’re not ready for flat config, import our defaults into a classic config:

module.exports = require('@bancame/eslint-config').default;

Then lint as usual:

npx eslint . --ext .js,.ts,.jsx,.tsx

Publishing to npm

To publish this package to npm, follow these steps:

  1. Update the version in package.json.

  2. Update the changelog in CHANGELOG.md with the new version and a summary of changes.

    • Use the format: ## [x.x.x] - YYYY-MM-DD
    • Example: ## [1.0.0] - 2025-06-02
    • Launch first release with support for eslint v9 and flat config.
  3. Create a new pull request with the version change.

  4. Wait for the CI to pass.

  5. Merge the pull request.