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-md

v1.1.7

Published

Opninionated ESLint and Prettier Custom Config

Downloads

2,883

Readme

eslint-config-md

npm version

These are the settings for ESLint and Prettier I use for my personal projects

Installation

You can use this config globally and/or locally per project.

It's best to install this locally once per project, that way you can have project specific settings as well as sync those settings with others working on your project via git.

Local / Per Project Install

  1. If you don't already have a package.json file, create one with npm init -y.

  2. Then we need to install everything needed by the config:

    npx install-peerdeps eslint-config-md@latest --dev
  3. You can see in your package.json there are now a big list of devDependencies.

  4. Create a .eslintrc.json file in the root of your project's directory (it should live where package.json does). Your .eslintrc.json file should look like this:

    {
      "extends": ["md"]
    }

    Tip: You can alternatively put this object in your package.json under the property "eslintConfig":. This makes one less file in your project.

  5. You can add two scripts to your package.json to lint and/or fix:

    "scripts": {
      "lint": "eslint . --ext .js,.ts",
      "lint:fix": "eslint . --ext .js,.ts --fix"
    },
  6. Now you can manually lint your code by running npm run lint and fix all fixable issues with npm run lint:fix. You probably want your editor to do this though.

Overriding

If you'd like to override eslint or prettier settings, you can add the rules in your .eslintrc.json file.

The ESLint rules go directly under "rules" while prettier options go under "prettier/prettier".

Note that prettier rules overwrite anything in this config (trailing comma, and single quote), so you'll need to include those as well.

{
  "extends": ["md"],
  "rules": {
    "prettier/prettier": [
      "error",
      {
        "printWidth": 120,
        "semi": true,
        "singleQuote": true,
        "tabWidth": 4,
        "trailingComma": "es5"
      }
    ]
  }
}

Overrides can also be added to React package.json.

Usage

With VS Code

You should read this entire thing. Serious!

Once you have done one, or both, of the above installs. You probably want your editor to lint and fix for you. Here are the instructions for VS Code:

  1. Install the ESLint package
  2. Now we need to setup some VS Code settings via Code/FilePreferencesSettings. It's easier to enter these settings while editing the settings.json file, so click the {} icon in the top right corner:
"editor.formatOnSave": true,
"[javascript]": {
  "editor.formatOnSave": false
},
"[javascriptreact]": {
  "editor.formatOnSave": false
},
"[typescript]": {
  "editor.formatOnSave": false
},
"[typescriptreact]": {
  "editor.formatOnSave": false
},
"eslint.workingDirectories": [
  {
    "mode": "auto"
  }
],
"editor.codeActionsOnSave": {
  "source.fixAll": true
}

With Create React App

  1. Run npx install-peerdeps --dev eslint-config-md
  2. Open your package.json and replace "extends": "react-app" with "extends": "md"

Not working

Start fresh. Sometimes npm modules can goof you up.

This will remove them all from the project.

npm remove eslint eslint-config-airbnb eslint-config-prettier eslint-plugin-html eslint-plugin-import eslint-plugin-jsx-a11y eslint-plugin-prettier eslint-plugin-react eslint-plugin-react-hooks prettier

Then, remove your package-lock.json file and delete the node_modules/ directory.

After uninstalled, follow the above instructions again from start.