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

@lasalefamine/eslint-config-base

v3.1.0

Published

Eslint JS sharable base config

Downloads

196

Readme

CI npm

@lasalefamine/eslint-config-base

Base config for ESlint - no React

Our default export contains all of our ESLint rules, including ECMAScript 6+. It requires eslint, eslint-plugin-import, eslint-plugin-simple-import-sort, @typescript-eslint/eslint-plugin, @typescript-eslint/parser and typescript

Install

First install the dependencies:

yarn add --dev eslint eslint-plugin-import eslint-plugin-simple-import-sort @typescript-eslint/eslint-plugin @typescript-eslint/parser typescript

Then add our config:

yarn add --dev @lasalefamine/eslint-config-base

Usage

@lasalefamine/eslint-config-base

Add to your .eslintrc

{
  "extends": "@lasalefamine/eslint-config-base",
  "parserOptions": {
    "project": "tsconfig.json"
  }
}

tsconfig.eslint.json

Create a new tsconfig.eslint.json files for overrides the include and exclude of your main tsconfig.json, so that ESLint will be able to lint everything without complaining:

{
  "extends": "./tsconfig.json",
  "exclude": [
    "node_modules"
  ],
  "include": [
    "**/*.js",
    "**/*.ts",
    "**/*.tsx"
  ]
}

And in your .eslintrc:

{
  "extends": "@lasalefamine/eslint-config-base",
  "parserOptions": {
    "project": "tsconfig.eslint.json"
  }
}

The parserOptions.project issue

You may wonder why you need to add an extra tsconfig.eslint.json file: this is kinda a problem with some rules that come from @typescript-eslint that need type information during the linting process, this is why you need to add a projectOptions.project to your .eslintrc. At this point ESLint will lint only files specified within the include array of the tsconfig you choose, this actually why you need to create a new tsconfig.eslint.json, extends your main tsconfig for having type information available to ESLint and then just re-include everythin you need to lint.

More info:

  • https://github.com/typescript-eslint/typescript-eslint/issues/856
  • https://github.com/typescript-eslint/typescript-eslint/issues/890

Develop

You can run tests with yarn test.

You can make sure this module lints with itself using yarn lint.