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

eslint-config-clean-code

v8.0.0

Published

ESLint Configuration for Clean Typescript Code

Downloads

9

Readme

eslint-config-clean-code

Linter rules for clean and fast TypeScript development

Why?

Because every TypeScript developer deserves not to think about code style and minor approaches.

Installation

  1. Pre-requisite: you need to have both ESLint and TypeScript installed, preferably locally.
  2. npm install --save-dev eslint-config-clean-code
  3. In your .eslintrc file at the project root, add extends: eslint-config-clean-code.
  4. Also add parserOptions: { project: 'path.to.tsconfig.json' }.
  5. Customise the rules if required.

Choices

TypeScript

Because we believe that quality software development is impossible without types.

Automatic Code Formatting

We consciously disable rules related to whitespace, indents, etc. and recommend using Prettier instead, as a complementary tool to your linter. Having wasted numerous workdays bickering about minor formatting issues, this is the only sane choice for all projects, in our opinion.

Consistency over Pluralism

There should be one straightforward way to do anything, and this consistency is enforced by the rules.