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

@m-one-dev/awesome-nest-eslint

v1.0.2

Published

Opinionated ESLint plugin with NestJS-aware rules used across m-one projects.

Readme

@m-one-dev/awesome-nest-eslint

Opinionated ESLint plugin with NestJS-aware, TypeScript-aware rules used across m-one projects.

Install

npm install -D @m-one-dev/awesome-nest-eslint
# or
pnpm add -D @m-one-dev/awesome-nest-eslint
# or
yarn add -D @m-one-dev/awesome-nest-eslint

Usage (flat config)

// eslint.config.ts
import awesomeNest from '@m-one-dev/awesome-nest-eslint';
import { defineConfig } from 'eslint/config';

export default defineConfig(
  // ... your other configs
  awesomeNest.configs.recommended,
);

configs.recommended registers the plugin and turns on:

| Rule | Severity | Files | |---|---|---| | awesome-nest/no-typeorm-finder-methods | error | all | | awesome-nest/payload-type-suffix | error | all | | awesome-nest/unique-endpoint-dtos | error | all | | awesome-nest/dto-must-extend-abstract-or-base | error | **/*.dto.ts, **/dto/**/*.ts |

configs.all enables every rule at error severity, no file scoping.

Rules

Requirements

All rules are TypeScript-aware. Your ESLint config must use @typescript-eslint/parser with a typed parser service:

parserOptions: {
  projectService: true,
  // or: project: ['./tsconfig.json'],
  tsconfigRootDir: import.meta.dirname,
}

Peer dependencies:

  • eslint >= 9
  • typescript >= 5.4
  • @typescript-eslint/parser >= 8

Development

pnpm install
pnpm build
pnpm test

Releasing

Releases are tag-driven. Bump the version in package.json, commit, then tag:

git add package.json
git commit -m "chore: bump version to x.y.z"
git tag vx.y.z
git push --follow-tags

The publish.yml workflow runs install → build → test → pnpm publish on every v* tag and pushes to npmjs.com using the NPM_TOKEN repository secret.