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

@calmdownval/eslint-config

v2.1.4

Published

This is a collection of ESLint rule configurations for some of the most common JS/TS workflows. It does not extend any other config packages, all configuration resides within this repository.

Downloads

21

Readme

@calmdownval/eslint-config

This is a collection of ESLint rule configurations for some of the most common JS/TS workflows. It does not extend any other config packages, all configuration resides within this repository.

Motivation

This package configures all available rules of ESLint itself and any plugins used. Any overrides and additional config packages, should you need any, must be applied after this config to take effect. This package is intended to serve as a solid base for new projects or new ESLint configurations. It (re-)sets all options of all rules even if they correspond to their current defaults to fixate their behavior as much as possible.

Usage

To use this config you will need to install ESLint and any plugins required by the configurations you choose to use.

yarn add --dev eslint @calmdownval/eslint-config

Then setup your .eslintrc file as described below.

Default Configuration

The default configuration. Configures ESLint core rules.

You should always include this configuration.

.eslintrc:

{
  "root": true,
  "extends": [
    "@calmdownval/eslint-config"
  ]
}

Import Configuration

Configuration for the import plugin.

.eslintrc:

{
  "root": true,
  "extends": [
    "@calmdownval/eslint-config",
    "@calmdownval/eslint-config/import"
  ]
}

Required dependencies:

  • @calmdownval/eslint-import-resolver
  • eslint-plugin-import

TypeScript Configuration

This configuration replaces some of the default rules to work with TypeScript and adds plenty additional rules that are TS-specific. Also configures the Import plugin to resolve TS paths correctly.

.eslintrc:

{
  "root": true,
  "extends": [
    "@calmdownval/eslint-config",
    "@calmdownval/eslint-config/typescript",

    // additionally, if using eslint-plugin-import:
    "@calmdownval/eslint-config/import",
    "@calmdownval/eslint-config/typescript/import"
  ]
}

Required dependencies:

  • @calmdownval/eslint-import-resolver
  • @typescript-eslint/eslint-plugin
  • @typescript-eslint/parser
  • eslint-plugin-import (optional)

Monorepos and other non-trivial projects may need to reconfigure:

  • the project parser option
  • the project resolver setting

A monorepo with workspaces under the packages directory might use the following configuration:

{
  "parserOptions": {
    "project": "./packages/*/tsconfig.json"
  },

  // additionally, if using eslint-plugin-import:
  "settings": {
    "import/resolver": {
      "@calmdownval/eslint-import-resolver": {
        "project": "./packages/*/tsconfig.json"
      }
    }
  }
}