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

eslint-config-phloose

v1.2.1

Published

This is my personal [ESLint](https://eslint.org) config that i've used over time in different projects. The base config extends `airbnb-base` and `eslint:recommended` configurations. Further the package contains configs for `node`, `jest`, `vue`, `typescr

Readme

eslint-config-phloose

This is my personal ESLint config that i've used over time in different projects. The base config extends airbnb-base and eslint:recommended configurations. Further the package contains configs for node, jest, vue, typescript and svelte.

Install

This configuration assumes that (ESLint is installed.

Peer dependencies:

npm i -D eslint

Config installation:

npm i -D eslint-config-phloose

Usage

To use it simply add it to the extends property in a projects .eslintrc-file:

module.exports = {
    extends: ["phloose"]
    rules: {
        /* settings... */
    }
}

The specialized configs can be referenced in the way phloose/<specialized> where specialized is one of jest, node, svelte, ts or vue

All specialized configurations extend the base config so it does not need to be listed when using one of them.

Recommended usage

For the best user experience regarding formatting and linting it is best to use prettier-eslint, which will run Prettier first and then ESLint.

Previously my workaround was to use Prettier as an ESLint plugin so that prettier errors would show up when running [ESLint] (https://eslint.org) and also be fixed by running ESLint either from VSCode or from the command line. It has been shown that this approach has its limits and i came to the conclusion that it is better to have one tool for a specific job:

  • Prettier just for formatting
  • ESLint for highlighting and fixing code style issues

To be in line with this configuration a .prettierrc-file with the following settings needs to be added to the root folder of a project (example uses .js-format):

module.exports = {
    arrowParens: "avoid",
    endOfLine: "auto",
    tabWidth: 4,
    trailingComma: "all",
    quoteProps: "consistent",
};

For the following Prettier needs to be installed:

npm i -D prettier

Use prettier-eslint from the command line

To use prettier-eslint with this configuration from the commandline run:

npm i -D prettier-eslint-cli eslint-prettier-config

which will install the CLI for prettier-eslint and a prettier specific ESLint config that disables certain conflicting ESLint rules.

Then add prettier to the end of the extends array in the .eslintrc-file (this is important!):

module.exports = {
    extends: ["phloose", "prettier"]
    rules: {
        /* additional rules */
    }
}

To run prettier-eslint e.g. on all js and ts files of the src folder and subfolders issue the following:

prettier-eslint --write "src/**/*.js"

Use Prettier ESLint VSCode extension

Install the prettier-eslint core package and the config mentioned already above:

npm i -D prettier-eslint eslint-prettier-config

Then install Prettier ESLint extension for VSCode and add a workspace configuration with the following content:

{
    "[<language>]": {
        "editor.defaultFormatter": "rvest.vs-code-prettier-eslint"
    },
    "editor.codeActionsOnSave": {
        "source.fixAll": true
    },
    "eslint.validate": [
        "<language>"
    ],
}

This way VSCode formats with Prettier and also hightlights and fixes ESLint errors for the respective filetype/language set in brackets.

The .eslintrc-file has to be configured like in the previous section.