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

@ildella/nostandard

v0.3.1

Published

Eslint standard for bad people.

Readme

NoStandard

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

The overall project structure has been taken from NeoStandard from which I also borrowed some additional base and style rules that despite were not in my original ruleset, were not causing any issue with my current projects. They have all been converted to the Golden Rule.

Usage

yarn add -D @ildella/nostandard

# Or
pnpm add -D @ildella/nostandard

# Or, if you are an horrible person:
npm install -D @ildella/nostandard

And this is and example on how to use it in your eslint-config.js.

import nostandard from '@ildella/nostandard'

export default [
  {
    name: 'Your project name',
    // ...
  },
  ...nostandard(),
  {
    // languageOptions: {...},
    // plugins: {...},
    // rules: {...}
  },
  {
    name: 'Testing config...',
    files: ['tests/**/*.*js'],
    // ...mytestlib.configs['flat/recommended'],
    // rules: {...},
  },
]

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 anytning 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.

What's in here?

For now only basic ESLint basic and Stylistic

I will consider adding more stuff here like Promise, eslint-plugin-import-x and security.

I will also create a NodeJS dedicated configuration, based on eslint-plugin-n, eslint-plugin-functional and eslint-plugin-unicorn, refactoring them out of my current projects into a companion library to NoStandard.