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

v1.2.1

Published

an eslint config designed to work with prettier

Downloads

11

Readme

eslint-config-slalom ⛷️

Travis

An eslint config built with prettier in mind, heavily based off of eslint-config-xo.

Install

yarn add eslint-config-slalom --dev

Usage

In package.json

{
  "name": "my-project",
  "eslintConfig": {
    "extends": "slalom"
  }
}

Or in .eslintrc

{
  "extends": "slalom"
}

Why another eslint config?

I wanted an eslint config to fit the following criteria:

  • doesn't require me to install multiple eslint plugins (e.g. eslint-config-airbnb)
  • doesn't require me to have unnecessary / unneeded plugins just to turn things off (e.g. eslint-config-prettier)
  • had a minimal, clean, but reasonable ruleset that enforces readable code (which is why this is based off of xo)
  • ...but also doesn't have extra/separate configs or plugins to extend certain rules (e.g. xo/react, xo/space, etc.)
  • reaches code-quality rules and leaves formatting to Prettier

This config:

  • contains no rules that conflict with Prettier, nor stylistic rules you can set to your liking with Prettier
  • does not require any other eslint config or plugin
  • focuses on readable code and code-quality rules
  • covers react and next-generation javascript

Recommended configuration

I use this with eslint-plugin-prettier to set formatting rules. I also recommend eslint-plugin-unicorn which checks a nice set of rules.

{
  "parser": "babel-eslint",
  "parserOptions": {
    "ecmaVersion": 6,
    "sourceType": "module"
  },
  "extends": ["slalom"],
  "plugins": ["prettier", "react", "unicorn"],
  "rules": {
    "prettier/prettier": [
      "error",
      {
        "singleQuote": true,
        "semi": false
      }
    ]
  }
}

Thanks

Sindre Sorhus XO Prettier