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

eslint-nostandard

v0.6.0

Published

Eslint standard for bad people.

Downloads

469

Readme

NoStandard

A consolidation of my old eslint configurations ported to ESLint 9+ and Flat configuration.

What's in here?

  • base — core ESLint rules for correctness and best practices
  • style — opinionated formatting via Stylistic
  • svelte — Svelte rules via eslint-plugin-svelte (optional, subpath import)
  • vitest — Vitest rules via @vitest/eslint-plugin (optional, subpath import)

Usage

yarn add -D eslint-nostandard
pnpm add -D eslint-nostandard
npm install -D eslint-nostandard

Basic usage for eslint.config.js:

import {nostandard} from 'eslint-nostandard'

export default [
  ...nostandard.recommended,  // base + style

  // Or pick individually:
  // nostandard.base,
  // nostandard.style,
]

Svelte

Install the optional peer dependency, then import from the subpath:

yarn add -D eslint-plugin-svelte svelte
import {nostandard} from 'eslint-nostandard'
import svelte from 'eslint-nostandard/svelte'

export default [
  ...nostandard.recommended,
  ...svelte,
]

Vitest

Install the optional peer dependency, then import from the subpath:

yarn add -D @vitest/eslint-plugin
import {nostandard} from 'eslint-nostandard'
import vitest from 'eslint-nostandard/vitest'

export default [
  ...nostandard.recommended,
  vitest,
]

Why not NeoStandard then?

There are too many useless dependencies. Especially I do not consider usable anything that gives for granted that developers use React, or any other specific framework. Why would I want anything JSX or React in my NodeJS or Svelte projects?

For the same reason, I do not want eslint-plugin-n as a default dependency.

Finally, they do not respect my golden rule.

Golden Rule

If it breaks, it's an error. If it does not break, it's a warning.

With one and only one special exception, as all good rules must have an exception.