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

@foray1010/eslint-config

v12.2.2

Published

It aims at providing a general eslint config for:

Downloads

812

Readme

@foray1010/eslint-config

It aims at providing a general eslint config for:

  1. assisting developer to obtain better code quality

  2. no opinion on coding styles, leave it to @foray1010/prettier-config

Versioning

X.Y.Z

X for requiring newer eslint or node (breaking changes)

Y for stricter rules

Z for looser rules

Installation

  1. yarn add -DE @foray1010/eslint-config eslint prettier

  2. Create an eslint.config.js in the project root

    • For general purpose or Node.js project (support TypeScript)

      import {
        eslintIgnoresConfig,
        eslintNodeConfig,
      } from '@foray1010/eslint-config'
      
      const config = [...eslintIgnoresConfig, ...eslintNodeConfig]
      export default config
    • For general frontend projects (support TypeScript)

      import {
        eslintIgnoresConfig,
        eslintBrowserConfig,
      } from '@foray1010/eslint-config'
      
      const config = [...eslintIgnoresConfig, ...eslintBrowserConfig]
      export default config
    • For frontend React projects (support TypeScript)

      import {
        eslintIgnoresConfig,
        eslintReactConfig,
      } from '@foray1010/eslint-config'
      
      const config = [...eslintIgnoresConfig, ...eslintReactConfig]
      export default config
    • You can apply config per different directories

      import {
        applyConfig,
        eslintIgnoresConfig,
        eslintNodeConfig,
        eslintReactConfig,
      } from '@foray1010/eslint-config'
      
      const config = [
        ...eslintIgnoresConfig,
        ...applyConfig(
          {
            filePrefixes: '.',
            ignores: ['src/**'],
          },
          eslintNodeConfig,
        ),
        ...applyConfig(
          {
            filePrefixes: ['src'],
          },
          eslintReactConfig,
        ),
      ]
      export default config
  3. If the project support ES Modules, you can directly use eslint command with the following setting in package.json.

    {
      "type": "module"
    }
  4. If the project does not support ES Modules, you have to put the config in eslint.config.mjs instead, and use the following npm script in package.json. Note that your editor may not support custom eslint config path and may not work properly.

    {
      "scripts": {
        "eslint": "ESLINT_USE_FLAT_CONFIG=true eslint --config eslint.config.mjs"
      }
    }

    then use npm run eslint or yarn eslint to replace eslint