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

@edgelogistics/eslint-plugin-backend-nodejs-typescript

v2.0.0

Published

ESLint config preset for Node.js + TypeScript backend projects at EdgeLogistics.

Readme

@edgelogistics/eslint-plugin-backend-nodejs-typescript

ESLint config preset for Node.js + TypeScript backend projects at EdgeLogistics.

Requisitos

  • eslint >= 8.x
  • typescript >= 4.7.x
  • @typescript-eslint/parser ^6.x (incluido como peer dependency)

Instalación

npm install @edgelogistics/eslint-plugin-backend-nodejs-typescript --save-dev

Uso

En tu .eslintrc.js:

module.exports = {
  extends: ['plugin:@edgelogistics/backend-nodejs-typescript/recommended'],
};

O si usas Flat Config (eslint.config.js):

const backendPlugin = require('@edgelogistics/eslint-plugin-backend-nodejs-typescript');

module.exports = [...backendPlugin.configs.recommended];

Desarrollo Local

Instalación de dependencias

npm install

Probar cambios localmente

Para probar el plugin en otro proyecto sin publicar a npm:

# 1. En el directorio del plugin, crear un link simbólico
npm link

# 2. En el proyecto que quiere usar el plugin
npm link @edgelogistics/eslint-plugin-backend-nodejs-typescript

Para desvincular:

# En el proyecto que usaba el plugin
npm unlink @edgelogistics/eslint-plugin-backend-nodejs-typescript

# En el directorio del plugin (opcional, para limpiar)
npm unlink

Usar directamente desde file: (alternativa a npm link)

En el package.json del proyecto que quiere usar el plugin:

{
  "devDependencies": {
    "@edgelogistics/eslint-plugin-backend-nodejs-typescript": "file:../eslint-backend-nodejs-typescript"
  }
}

Luego:

npm install

Lint y format del propio plugin

npm run lint    # Solo lint
npm run format  # Format + lint fix

Publicar a npm

Este proyecto usa semantic-release para releases automáticos.

Flujo de release

  1. Haz tus cambios en una rama
  2. Commitea siguiendo Conventional Commits:
    • feat: nuevo rule → patch release
    • fix: correccion de bug → patch release
    • feat!: cambio breaking → major release
  3. Haz merge a master (via PR)
  4. El pipeline ejecutará npm run release automáticamente

Release manual

npm run release

Esto publicá a npm usando el versionado semántico basado en los commits.

Estructura del proyecto

src/
├── index.js      # Entry point del plugin
├── plugins.js    # Lista de plugins que se importan
├── rules.js      # Todas las reglas configuradas
└── config.js     # Configuración del preset 'recommended'

Changelog

Ver CHANGELOG.md para el historial de versiones.