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

@fenge/eslint-config

v0.1.1

Published

A super strict eslint config for linting js/ts/package.json.

Downloads

270

Readme

@fenge/eslint-config

PRs Welcome

A strict eslint config preset containing a comprehensive set of rules for linting js / ts / package.json files. Based on standard.js without any stylistic opinions.

Feature

  • Lint js / mjs / cjs / jsx / ts / mts / cts / tsx / package.json files only.
  • Strict. More than 300+ rules.
  • Highly customizable by omitting unwanted.
  • Type safe. TypeScript friendly.
  • Pure JavaScript project friendly.
  • React friendly.
  • NestJS friendly.
  • Based on standard.js, introduced more stricter rules.
  • Have no stylistic opinions. Prettier friendly.
  • Respect .gitignore.
  • ESLint Flat config, compose easily!
  • Modern. ESM first.
  • One-line of config.

Usage

Install it in the root of js / ts project.

npm install -D eslint @fenge/eslint-config

Config eslint.config.js (for ESM).

import config from "@fenge/eslint-config";

export default config;

If you are in CommonJS, config eslint.config.js bellow:

module.exports = import("@fenge/eslint-config");

Config package.json

{
  "scripts": {
    "lint": "eslint .",
    "lint:fix": "eslint . --fix"
  }
}

Note: TypeScript project is required a tsconfig.json file in the root.

Advanced Usage

Config Builder

You can use Builder class to customize for selecting or omitting some rules.

import { Builder } from "@fenge/eslint-config";

export default new Builder()
  .enablePackagejson({
    pick: ["packagejson/top-types"], // only these rules will work for package.json files
  })
  .enableJavascript({
    omit: ["no-var"], // these rules will not work for js files
  })
  .enableTypescript({
    project: "tsconfig.json", // tsconfig.json path
    extend: {
      // apply additional rules for ts files
      "@typescript-eslint/no-explicit-any": "error",
      "@typescript-eslint/consistent-type-assertions": [
        "error",
        { assertionStyle: "never" },
      ],
      "@typescript-eslint/no-non-null-assertion": "error",
    },
  })
  .toConfig();

License

MIT