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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@nkzw/eslint-config

v1.18.1

Published

ESLint config with sensible defaults.

Downloads

8,263

Readme

@nkzw/eslint-config

Opinionated ESLint config with sensible defaults.

Installation & Usage

npm install @nkzw/eslint-config

In your .eslintrc.js or .eslintrc.cjs:

module.exports = {
  extends: ['@nkzw'],
};

Then run pnpm eslint . or npm eslint ..

Philosophy & Principles

Use this configuration if these principles resonate with you:

  • Error, Never Warn: People tend to ignore warnings. There is little value in only warning about potentially problematic code patterns. Either it's an issue or not. Errors force the developer to address the problem either by fixing it or explicitly disabling the role in that location.
  • Strict, consistent code style: If there are multiple ways of doing something, or there is a new language construct or best practice, this configuration will suggest the most strict and consistent solution.
  • Prevent Bugs: Problematic patterns such as instanceof are not allowed. This forces developers to choose more robust patterns. This configuration disallows usage of console or test.only so that you don't end up with unintended logging in production or CI failures. If you want to log to the console in your production app, use another function that calls console.log to distinguish between debug logs and intentional logs.
  • Fast: Slow rules are avoided if possible. For example, it is recommended to use the fast noUnusedLocals check in TypeScript instead of the no-unused-vars rules.
  • Don't get in the way: Rules that get in the way or are too subjective are disabled. Rules with autofixers are preferred over rules without them.

Included Plugins & Rules

This configuration consists of the most useful and least annoying rules from the following eslint plugins:

Suggestions

This configuration is meant to be used with:

Read more frontend tooling suggestions in this blog post.