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

@lytovka/eslint-config

v1.4.1

Published

ESLint rules configuration according to Ivan Lytovka's preference.

Downloads

80

Readme

@lytovka/eslint-config

npm

Installation

This module is distributed via npm and should be installed as one of your project's devDependencies. You should also have required eslint peerDependency installed.

npm i -D eslint @lytovka/eslint-config

Usage

Then, add the extends to your .eslintrc.js:

module.exports = {
  extends: ["@lytovka"],
  rules: {
    // override rules if needed
  },
}

In addition, you can add scripts to your package.json to identify errors and warnings. For example:

{
  "scripts": {
    "lint": "eslint --max-warnings 0 --cache --cache-location ./node_modules/.cache/.eslintcache --ext js,jsx,ts,tsx .",
    "lint:fix": "eslint --fix ."
  }
}

Other configs

Currently this module exposes a few additional configs:

  • @lytovka/eslint-config/react: preset for React projects.
  • @lytovka/eslint-config/jsx-a11y: preset for accessibility issues in React apps.
  • @lytovka/eslint-config/import: preset for import rules (both JavaScript and TypeScript projects).

Feel free to add those configs to the extend property:

module.exports = {
  extends: [
    "@lytovka",
    "@lytovka/eslint-config/react",
    "@lytovka/eslint-config/jsx-a11y",
    "@lytovka/eslint-config/import"
  ],
  rules: {
    // override rules
  },
}

TypeScript rules

By default, this module will search for tsconfig.json in the project root to determine if TypeScript ESLint rules should be enabled. Alternatively, you can overwrite the ESLINT_TSCONFIG_PATH environment variable to scan for a different file. For example:

// .eslintrc.js
process.env.ESLINT_TSCONFIG_PATH = "tsconfig.eslint.json"

module.exports = {
  extends: ["@lytovka"]
}