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

@cuzom/eslint-config

v1.2.0

Published

ESLint flat config: recommended JavaScript and TypeScript rules, light typing, formatting left to Prettier.

Readme

@cuzom/eslint-config

Cuzom Oy's ESLint flat config: the recommended JavaScript and TypeScript rules, light typing, and formatting left to Prettier.

pnpm add -D eslint typescript @cuzom/eslint-config

eslint.config.js:

import cuzom from '@cuzom/eslint-config'

export default [
  ...cuzom,
  // project rules and ignores
]

Light typing. Inference over annotations, no enums (a union of string literals instead), any warns, @ts-expect-error needs a reason, and type-only imports are marked. Everything Prettier handles is turned off through eslint-config-prettier.

Vue and Nuxt. Use Nuxt's own config and add the light-typing rules and Prettier last:

// @ts-check
import { lightTypes } from '@cuzom/eslint-config'
import prettierConfig from 'eslint-config-prettier'
import withNuxt from './.nuxt/eslint.config.mjs'

// The light-typing rules need the TypeScript parser, so they apply to TypeScript and Vue files only.
export default withNuxt({ files: ['**/*.{ts,vue}'], ...lightTypes }, prettierConfig)

Without the files line the type-aware rules also run on plain .js and .mjs files, including this config file, and ESLint stops with "You have used a rule which requires type information".

.nuxt/eslint.config.mjs is generated by Nuxt, so give the app "postinstall": "nuxt prepare" in its package.json: eslint then works right after an install, with no typecheck run first.

Also exported: ignores (build output and tool folders).

Needs ESLint 10 and TypeScript 6; typescript-eslint does not support TypeScript 7 yet.

© Cuzom Oy. Apache-2.0. Source: cuzom-dev/dev-config.