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

@mniebling/lint-config

v0.3.0

Published

My personal linting configuration

Readme

@mniebling/lint-config

npm

Autoformat on save is a useful time saver and integrating a formatter with AI tooling is very effective to get output code looking correct. However, Prettier is too opinionated; it wraps lines in weird ways and enforces some suboptimal patterns. This tradeoff is tolerable for writing code on a large team, but not for working on my personal projects.

See: https://antfu.me/posts/why-not-prettier

Installation

npm install --save-dev \
  @mniebling/lint-config \
  oxlint \
  oxlint-tsgolint \
  @stylistic/eslint-plugin

Usage

Create an oxlint.config.ts in the project root:

import myConfig from '@mniebling/lint-config'
import { defineConfig } from 'oxlint'

export default defineConfig({
  extends: [myConfig],
})

Project-specific rules can be added alongside extends and will override the shared config:

import myConfig from '@mniebling/lint-config'
import { defineConfig } from 'oxlint'

export default defineConfig({
  extends: [myConfig],
  rules: {
    'no-console': 'warn',
  },
})

Type-aware linting

Type-aware linting is enabled via options.typeAware: true. This requires oxlint-tsgolint to be installed and running alongside oxlint. See the Oxlint type-aware linting docs for more info.