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

@guidecx/config-eslint

v0.0.1-alpha.0

Published

The configuration files for ESLint used by all GuideCX Applications

Downloads

1

Readme

GCX Eslint Configuration

NOTE: This package is dependent on having multiple dependencies installed (some of which are optional, based on which sub-config files you use). You should have the following dependencies installed and set up:

  • @guidecx/config-prettier
  • husky
  • lint-staged
  • npm-run-all
  • typescript

Installing configuration files into another project

This packages has a few different exports you can use in your application. There are configuration files of the following type:

  • base (core javascript)
  • graphql
  • jest
  • react
  • typescript

In your project, you can do the following to include these linting rules:

  1. at the root of the other project, install the package with npm install --save-dependency @guidecx/config-eslint
  2. in your projects eslintrc.js file, include the following configuration options:
    'extends': [
      '@guidecx/config-eslint/base', // replace these lines with whatever config files you need from the list above
      '@guidecx/config-eslint/typescript'
      '@guidecx/config-eslint/react'
    ]
  3. note: some of the configs in the package have dependencies that you need to set up as well. For example, if you're using the typescript lint file, you need to set up typescript in your project before the linter can run. At the very least, you'll need to run npm install --save-dev husky lint-staged npm-run-all typescript
  4. once you've installed all the proper dependencies, you can test that the linting works by running npx eslint {filename} in your local repo. If everything is set up properly, you will see warnings and errors from eslint (assuming your code has them).
  5. now that things are working manually, its time to run these automatically as a pre-commit husky hook (using lint-staged)
  6. install both husky and lint-staged. according to the lint-staged docs, the easiest way to install husky and lint-staged together is by running npx mrm lint-staged.
  7. add the following config options to your package.json:
      "devDependencies": { // don't overwrite the versions installed on step 3
        "husky": "^4.3.7",
        "lint-staged": "^10.5.3",
        "npm-run-all": "^4.1.5",
        "typescript": "^3.7.5" // if you're in a vanillaJS project, you don't need this installed, but should also update the `validate` script below to not use `tsc`
      },
      "scripts": {
        "tsc": "tsc",
        "lint": "eslint 'src/**/*.{ts,tsx,js,jsx}'",
        "format": "prettier 'src/**/*.{ts,tsx,js,jsx,json,graphql}'",
        "format:write": "npm run format --list-different --write",
        "format:check": "npm run format --check",
        "validate": "npm-run-all --parallel -c format:check \"lint --quiet\" tsc test"
      },
      "lint-staged": {
        "src/**/*.{ts,tsx,js,jsx,graphql}": [
          "npm run format:write",
          "git add"
        ]
      },
      "husky": {
        "hooks": {
          "pre-commit": "lint-staged"
        }
      }
  8. prettier and eslint should now be running every time you commit code via git!