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

@goparrot/eslint-config

v1.2.0-dev.2

Published

GoParrot shared eslint configuration

Downloads

473

Readme

How to use

npm install --save-dev @goparrot/eslint-config

Installed libraries out of the box:

Choose the right set of rules

Create the .eslintrc.js file in the directory next to package.json

module.exports = {
  extends: ["@goparrot/eslint-config/recommended"],
  parserOptions: {
    project: "./tsconfig.eslint.json",
  },
  rules: {
    // rules to override.
  },
};

You should create the tsconfig.eslint.json in your project.

See the examples of tsconfig.json and tsconfig.eslint.json in this repository.

Choose the right set of rules

Common recommended rules:

extends: ['@goparrot/eslint-config/recommended']

Less strict rules:

extends: ['@goparrot/eslint-config/recommended', '@goparrot/eslint-config/less-strict']

For a frontend project with react and jsx:

npm install --save-dev eslint-plugin-react eslint-plugin-react-hooks
extends: ['@goparrot/eslint-config/recommended', '@goparrot/eslint-config/react', '@goparrot/eslint-config/jsx']

Create the .eslintignore file in the directory next to .eslintrc.js

# you must any dot `.file` which you want to ignore
# by default we don't ignore hidden `!.*.js` and `!.*.json` files in the root directory (for example: `.commitlintrc.js`, .`prettierrc.json`)
# example: if you don't want to ignore these files
!.eslintrc.js

# don't forget to add here all ignored folders or files from .gitignore that you don't need to check with a linter (there is no magic)
# by default we ignore `node_modules` and `.yalc` folders in the root directory
# example: if you want to ignore these files or directories
dist
coverage
test-reports
.nyc_output
.bit

add npm scripts

{
  "scripts": {
    "prettier": "npm run prettier:base -- '**/**.+(md)'",
    "prettier:base": "prettier --ignore-path .eslintignore --write",
    "format": "npm run prettier && npm run lint -- --fix",
    "format:base": "npm run lint:base -- --fix",
    "format:staged": "git add . && lint-staged --allow-empty -q",
    "lint": "npm run lint:base -- './**/**.{ts,tsx,js,jsx,json}'",
    "lint:base": "npm run lint:config:check && eslint",
    "lint:config:check": "eslint-config-prettier src/index.ts",
    "typecheck": "tsc -p tsconfig.json --noEmit"
  }
}

Make sure to

  • call the linter on the pre-commit hook
  • configure prettier to be called automatically when saving a file in the Webstorm or vscode