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

@redguy12/eslint-config

v1.0.2

Published

My ESLint Style Guide

Downloads

5

Readme

@redguy12/eslint-config

My ESLint Style Guide

Adding To A Project

  1. Note: this project is meant to be used alongside @redguy12/prettier-config so install & configure that first.

  2. Install the config by running:

    npm install @redguy12/eslint-config @rushstack/eslint-patch @types/eslint eslint --save-dev
  3. Add an .eslintrc.js file (or .eslintrc.cjs if you are using Node and ESM in the rest of your project) with the following content:

    /** @file ESLint Configuration file. */
    
    "use strict";
    
    require("@rushstack/eslint-patch/modern-module-resolution");
    
    /** @type {import("eslint").Linter.Config} */
    const config = {
    	extends: "@redguy12",
    
    	overrides: [
    		{
    			files: "!**.md/*",
    			parserOptions: { project: "./jsconfig.json" },
    		},
    	],
    
    	root: true,
    };
    
    module.exports = config;
  4. Add more overrides for specific files. Keep !**.md/* (added in the previous step) last.

    [
    	{
    		extends: "@redguy12/typescript",
    		// TypeScript files
    		files: "**.ts",
    	},
    	{
    		extends: "@redguy12/node",
    		// Node.JS scripts
    		files: [],
    	},
    	{
    		extends: "@redguy12/esm",
    		// ESM files
    		files: "**.mjs",
    	},
    	{
    		extends: "@redguy12/cli",
    		// CLIs (including JS GitHub Actions)
    		files: ["bin/**.js", ".github/**.js"],
    	},
    	{
    		extends: "@redguy12/config",
    
    		// Configuration files
    		files: [
    			"**.config.js",
    			"**rc.js",
    			"**.config.mjs",
    			"**rc.mjs",
    			"**.config.cjs",
    			"**rc.cjs",
    		],
    	},
    	{
    		extends: "@redguy12/browser",
    		// Client-side scripts (including HTML files)
    		files: ["**.html", "**.htm", "**.vue"],
    	},
    	{
    		extends: "@redguy12/sample",
    		// Files including samples (AKA docs) (including HTML and Markdown files)
    		files: ["**.md", "**.md/*"],
    	},
    	{
    		extends: "@redguy12/vue",
    		// Vue SFCs (v3)
    		files: "**.vue",
    	},
    ];

    You can remove any objects that have an empty or unchanged files array. However, make sure that the entries stay in this order.

  5. Add project-specific configuration (such as ecmaVersion or you can change the parserOptions.project). You should not need to add more rules; it'd probably be better to update the config in that case. Note that ecmaVersion is overridden in some configs, so you may need to put it in the !**.md/* entry.

  6. Add an npm script to lint your code as so:

    "lint:eslint": "cd \"node_modules/@redguy12/eslint-config/\" && npx eslint ../../../ --resolve-plugins-relative-to . --fix && cd \"../../../\""
  7. To lint your code, simply run

    npm run lint:eslint

Congrats! You've successfully integrated ESLint into your project with @redguy12/eslint-config!

For All

While this was made specifically for me, anyone can use it! If you have any feedback or require support, please open a discussion and I will get back to you as soon as I can.

Contributing

Feel free to open pull requests, but don't be surprised when we close them. This project rarely changes. However, if you really feel like it should change, open an issue so we can discuss it!