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

@lumston/eslint-config-lumston

v1.1.0

Published

Shared configurations for cleancode to lumston

Downloads

2,141

Readme

Status GitHub Issues GitHub Pull Requests License


📝 Tabla de contenidos

🧐 Acerca de

Este proyecto busca mejorar las practicas de nuestros desarrolladores y empujarlos a desarrollar codigo de calidad y con las mejores practicas.

🏁 Empezando

Estas instrucciones te ayudaran a configurar las reglas definidas por lumston para cumplir con nuestros estandares de clean code.

Prerequisitos

Tener instalado eslint y configurado para tu proyecto de typescript. Este es un ejemplo del archivo: eslintrc.js, que debe de estar en la carpeta raiz y su configuracion recomendada.

module.exports = {
  parser: '@typescript-eslint/parser',
  parserOptions: {
    project: 'tsconfig.json',
    tsconfigRootDir: __dirname,
    sourceType: 'module',
  },
  plugins: ['@typescript-eslint/eslint-plugin'],
  extends: [
    'plugin:@typescript-eslint/recommended',
    'plugin:prettier/recommended',
  ],
  root: true,
  env: {
    node: true,
    jest: true,
  },
  ignorePatterns: ['.eslintrc.js'],
  rules: {
    
  }
};

👨🏻‍💻 Instalacion

npm i @lumston/eslint-config-lumston

En nuestro archivo eslintrc.js, en nuestra key extends agregamos el nombre del paquete

'@lumston/eslint-config-lumston'

🎈 Uso

Este es un ejemplo, de como deberia de quedar configurado el archivo

module.exports = {
  parser: '@typescript-eslint/parser',
  parserOptions: {
    project: 'tsconfig.json',
    tsconfigRootDir: __dirname,
    sourceType: 'module',
  },
  plugins: ['@typescript-eslint/eslint-plugin'],
  extends: [
    'plugin:@typescript-eslint/recommended',
    'plugin:prettier/recommended',
   '@lumston/eslint-config-lumston'
  ],
  root: true,
  env: {
    node: true,
    jest: true,
  },
  ignorePatterns: ['.eslintrc.js'],
  rules: {
    
  }
};

⛏️ Construido usando

✍️ Autores

Tambien puedes revisar la lista de contribuyentes contribuyentes que participaron en el proyecto.

🎉 Reconocimientos

  • https://eslint.org/docs/latest/extend/shareable-configs