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

@koshikishi/eslint-config

v3.0.0

Published

ESLint shareable config

Downloads

31

Readme

@koshikishi/eslint-config

NPM Version GitHub License Check Workflow Status

The ESLint shareable config designed for my personal projects.

Use it as is or as a foundation for your own configuration file.

Installation

Install the package and eslint in your project:

npm i -D eslint @koshikishi/eslint-config

Plugins

This config bundles the following plugins and uses additional rules from them:

All plugins are direct dependencies and will be installed automatically.

Usage

This config is designed to validate Vanilla JS and Node.js projects and only supports flat (eslint.config.js) configuration files.

For validating your Vanilla JS project use the default config:

import config from '@koshikishi/eslint-config';
import globals from 'globals';

export default [
  ...config,
  {
    languageOptions: {
      globals: globals.browser,
    },
  },
];

For validating your Node.js project use the node config:

import config from '@koshikishi/eslint-config/node';
import globals from 'globals';

export default [
  ...config,
  {
    languageOptions: {
      globals: globals.node,
    },
  },
];

Extending the config

Add a rules key to your config, then add your overrides and additions there.

For example, to add the no-eval rule and turn off the no-console rule:

import config from '@koshikishi/eslint-config';
import globals from 'globals';

export default [
  ...config,
  {
    languageOptions: {
      globals: globals.browser,
    },
    rules: {
      'no-eval': 'error',
      'no-console': 'off',
    },
  },
];

You can also override the additional rules from plugins:

import config from '@koshikishi/eslint-config/node';
import globals from 'globals';

export default [
  ...config,
  {
    languageOptions: {
      globals: globals.node,
    },
    rules: {
      '@stylistic/quotes': ['error', 'double'],
      'n/file-extension-in-import': 'off',
    },
  },
];

Integration with VS Code

  1. Install the ESLint extension for VS Code.
  2. Install eslint and this config in your project following the Installation section.
  3. Add an ESLint configuration file (eslint.config.js) and extend it with this shareable config following the Usage section.

Note: since support for the flat config system in VS Code ESLint extension is still experimental, you may need to enable it using the eslint.experimental.useFlatConfig setting.

Useful links