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

v2.5.3

Published

ESLint Config from Devin Metivier

Downloads

74

Readme

npm npm

Opinionated ESLint Setup

These are my settings for ESLint and Prettier for Eslint

If you like them, awesome. If not, change them up!

What this does

  • Lints JavaScript based on the latest standards
  • Fixes issues and formatting errors with Eslint + Prettier
  • Lints + Fixes JSX markup

Installing

You can use eslint globally and/or locally per project. It's usually 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 or yarn init.

  2. Install everything needed by the config:

    npm install eslint-config-devjmetivier or yarn add eslint-config-devjmetivier

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

    {
      "extends": ["devjmetivier"]
    }

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

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

    "scripts": {
      "lint": "eslint . --ext .js,.ts,.jsx,.tsx",
      "lint:fix": "eslint . --ext .js,.ts,.jsx,.tsx --fix"
    }
  5. 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 automagically, though.