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

@fohte/eslint-config

v0.1.1

Published

ESLint config for fohte

Readme

@fohte/eslint-config

Personal ESLint configuration package with TypeScript support.

Installation

npm install @fohte/eslint-config

Installation

npm install --save-dev @fohte/eslint-config

# Install peer dependencies
npm install --save-dev eslint @typescript-eslint/eslint-plugin @typescript-eslint/parser eslint-config-prettier eslint-plugin-import eslint-plugin-simple-import-sort

# Optional: If using TypeScript
npm install --save-dev typescript

Usage

eslint.config.js:

import { mainConfig, typescriptConfig } from '@fohte/eslint-config'

export default [
  ...mainConfig,
  ...typescriptConfig,
]

Development

Setup

# Install dependencies
npm install

# Build TypeScript
npm run build

# Watch mode
npm run watch

Scripts

  • npm run build - Compile TypeScript files
  • npm run watch - Watch mode for development
  • npm run lint - Run ESLint on source files
  • npm run test - Run build and lint

Project Structure

src/
├── index.ts         # Main export
├── main.ts          # Base ESLint configuration
├── typescript.ts    # TypeScript-specific configuration
└── types/           # Type definitions for untyped packages

Release Process

This project uses release-please for automated releases.

1. Create a feature branch and make changes

  • Create a new branch from master
  • Make your changes (commit messages don't need to follow any specific format)

2. Create a PR and merge to master

  • Push your branch and create a PR
  • PR title must follow Conventional Commits:
    • fix: for bug fixes (patch release)
    • feat: for new features (minor release)
    • feat!: or fix!: for breaking changes (major release)
  • After review, merge the PR (squash merge only)

3. Automated release process

When changes are merged to master, release-please automatically:

  • Creates/updates a Release PR
  • Updates version in package.json
  • Updates CHANGELOG.md
  • When the Release PR is merged:
    • Creates GitHub release and git tag
    • Publishes to npm

Pre-commit Hooks

This project uses pre-commit hooks to ensure code quality. The hooks will automatically run when you commit changes.