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

@schuijers/eslint-config

v1.4.0

Published

ESLint rules according to schuijers' personal preference.

Downloads

5

Readme

@schuijers/eslint-config GitHub Build Status npm MIT License

My shareable ESLint configs.

Installation

# npm
npm install --save-dev @schuijers/eslint-config

# yarn
yarn add --dev @schuijers/eslint-config

# pnpm
pnpm add --save-dev @schuijers/eslint-config

This library has a required peerDependencies listing for eslint.

Usage

Reference @schuijers/eslint-config in your .eslintrc.js.

module.exports = {
  extends: '@schuijers/eslint-config',
  rules: {
    // your overrides
  },
}

Or, you can use it in other ways as described in the official documentation.

Other configs

Besides the base config (for JavaScript and TypeScript) this package also exposes some additional configs:

| Config name | Description | | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------- | | promise | Additional rules for projects that use promises | | vue | Additional rules for projects that use Vue | | nuxt | Additional rules for projects that use Nuxt (this config extends the vue config above) | | jest | Additional rules for projects that use Jest (with or without the Testing Library) | | cypress | Additional rules for projects that use Cypress |

You can use them standalone:

module.exports = {
  extends: '@schuijers/eslint-config/<config-name>',
}

Or in combination with the base config (recommended):

module.exports = {
  extends: [
    '@schuijers/eslint-config',
    '@schuijers/eslint-config/<config-name>',
  ],
}

Configuring aliases

When using aliases like @ or ~ in your project, you might run into import/no-unresolved errors when using this config. You can fix these errors by configuring the eslint-import-resolver-alias plugin (provided as a dependency by this package) through your ESLint config.

For example:

module.exports = {
  ...
  settings: {
    'import/resolver': {
      alias: {
        extensions: ['.js', '.vue'],
        map: [
          ['@', './src'],
          ['~', './src'],
        ],
      },
    },
  },
}

In this example, @ and ~ will be mapped to the /src folder for .js and .vue and files.

TypeScript

When using TypeScript and

  • a tsconfig that is not located in the root of your project, or
  • multiple tsconfigs (useful for monorepos)

you will need to configure the eslint-import-resolver-typescript plugin (provided as a dependency) through your ESLint config:

module.exports = {
  ...
  settings: {
    'import/resolver': {
      typescript: {
        // use <root>/path/to/folder/tsconfig.json
        "project": "path/to/folder",

        // Multiple tsconfigs

        // use a glob pattern
        "project": "packages/*/tsconfig.json",

        // use an array
        "project": [
          "packages/module-a/tsconfig.json",
          "packages/module-b/tsconfig.json"
        ],

        // use an array of glob patterns
        "project": [
          "packages/*/tsconfig.json",
          "other-packages/*/tsconfig.json"
        ]
      },
  },
}

License

MIT © Martijn Schuijers