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

@moritz-grimm/eslint-config-moritz-grimm

v1.0.1

Published

My preferred eslint config

Readme

eslint-config-moritz-grimm

My preferred ESLint config for JavaScript and TypeScript projects.

Disclaimer: This config is built for my personal use. There might be rough edges or opinionated choices that don't fit your workflow. Feel free to use it, but adjust it to your workflow.


Features

  • TypeScript support with type-checked rules
  • Stylistic rules via @stylistic/eslint-plugin
  • ESLint 9 Flat Config format
    • Modular: Import only what you need

Installation

npm install --save-dev @moritz-grimm/eslint-config-moritz-grimm

Requirements

  • Node.js: >=18.0.0
  • ESLint: >=9.0.0
  • TypeScript: >=5.0.0 (only if linting TypeScript files)

If you don't have ESLint or TypeScript installed yet:

npm install --save-dev eslint typescript

Configuration

This config is modular. You can import everything or only specific parts.

Option 1: Full Config (Recommended)

Import all rules (base + stylistic + TypeScript):

import eslintConfig from "eslint-config-moritz-grimm";

export default [
    ...eslintConfig,
];

Option 2: Modular Import

Pick only what you need:

Base rules (core JavaScript/TypeScript linting):

import eslintConfig from "eslint-config-moritz-grimm/base";

export default [
    ...eslintConfig,
];

Stylistic rules (code formatting):

import eslintConfig from "eslint-config-moritz-grimm/stylistic";

export default [
    ...eslintConfig,
];

TypeScript rules (type-checked linting):

import eslintConfig from "eslint-config-moritz-grimm/typescript";

export default [
    ...eslintConfig,
];

You can also combine multiple modules:

import baseConfig from "eslint-config-moritz-grimm/base";
import stylisticConfig from "eslint-config-moritz-grimm/stylistic";

export default [
    ...baseConfig,
    ...stylisticConfig,
];

Usage

Add these scripts to your package.json:

{
  "scripts": {
    "lint": "eslint .",
    "lint:fix": "eslint . --fix"
  }
}

Then run:

npm run lint        # Check for linting issues
npm run lint:fix    # Auto-fix issues

What's Included?

For a complete list of all rules and their configuration, see RULES.md.

Quick overview:

  • Code Quality: Strict equality, no unreachable code, prefer const, no duplicate imports
  • TypeScript: Type-checked linting, any warnings, promise handling
  • Code Style: 4-space indentation, semicolons, double quotes, 1TBS brace style, trailing commas


License

MIT