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

@jessety/eslint-config

v2.4.1

Published

ESLint config for TypeScript or JavaScript by @jessety

Downloads

661

Readme

@jessety/eslint-config

Yet another ESLint Shareable Config for TypeScript or JavaScript projects.

ci npm license

Install

npm install --save-dev eslint @jessety/eslint-config

Usage

Shareable configs work by leveraging the extends feature in your ESLint configuration. Once the package is installed, define extends to @jessety.

For example, a valid .eslintrc.json file could be:

{
  "extends": "@jessety"
}

The eslint-config suffix may be omitted because it is assumed by ESLint.

Configurations

This package contains the following sharable configurations:

  • base - Core rules for TypeScript node projects. Does not require TypeScript build. Fast.
  • strict - Stricter rules for TypeScript node projects. Requires type checking. Slower than base.
  • react - Rules for a React project
  • javascript - ESLint rules for JavaScript projects

As of version 2.x.x, base is the default export for .ts files, and javascript is the default for .js, .mjs, or .cjs files. To request one or the other, specify which in the eslintrc file. For example, a .eslintrc.json file that uses react configuration may look like this:

{
  "extends": "@jessety/eslint-config/react"
}

A project that uses a mix of both TypeScript and JavaScript may look like this:

{
  "overrides": [
    {
      "files": ["**/*.ts"],
      "extends": "@jessety"
    },
    {
      "files": ["**/*.{js,cjs,mjs}"],
      "extends": "@jessety/eslint-config/javascript"
    }
  ]
}

The base and strict configuration require typescript and eslint as peer dependencies. The javascript configuration only requires eslint.

License

MIT © Jesse Youngblood