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

eslint-config-molindo

v8.0.0

Published

Molindo ESLint config that implements our styleguide and helps to catch errors.

Downloads

2,730

Readme

eslint-config-molindo

Goals

  1. Find errors that are detectable with static analysis.
  2. Make reading code easier by providing consistent code style.
  3. Make writing code faster by leveraging auto fix wherever possible.

Getting started

  1. yarn add eslint eslint-config-molindo prettier --dev
  2. Setup your project config in eslint.config.mjs:
import {getPresets} from 'eslint-config-molindo';

export default [
  ...(await getPresets(
    // Base config
    'typescript', // or 'javascript'

    // Optional extensions
    'react',
    'cssModules',
    'tailwind',
    'jest',
    'cypress',
    'vitest'
  )),

  {
    // Your custom config
  }
];
  1. If you require globals, like browser APIs on window, you can add them to your config:
// eslint.config.mjs
import globals from 'globals';

export default [
  // ...
  {
    languageOptions: {
      globals: {
        ...globals.browser,
        ...globals.node
      }
    }
  }
];
  1. To set up Prettier, add to your package.json:
"prettier": "eslint-config-molindo/.prettierrc.json"
  1. If you use TypeScript, add to your tsconfig.json:
"extends": "eslint-config-molindo/tsconfig.json"

Happy linting!

Further configuration

CI integration

To validate your code in a CI pipeline, add the following to your package.json:

"scripts": {
  "lint": "eslint src && prettier src --check"
}

VSCode integration

The following two extensions are recommended:

  1. dbaeumer.vscode-eslint
  2. esbenp.prettier-vscode

To auto-fix errors from ESLint as well as Prettier on save, you can use the following configuration:

// settings.json (VSCode)
{
  "editor.codeActionsOnSave": {
    "source.fixAll.eslint": "always"
  },
  "editor.defaultFormatter": "esbenp.prettier-vscode",
  "editor.formatOnSave": true
}

Versioning

  • Patch releases are for improved documentation, fixing a rule to stop reporting false positives and internal code changes.
  • Minor releases are for changes to rules that can automatically be fixed.
  • Major releases happen when rules are changed that can't be fixed automatically.