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

eslint-config-comfycase

v1.0.0

Published

Comfiest ESLint Settings

Downloads

9

Readme

npm GitHub

ComfyCase

Comfiest ESLint Settings!

ComfyCase prefers spaces between parentheses, camelCase syntax except for object properties, double quotes, Stroustrup style braces, and indentation with tabs.

Instafluff

Like these projects? The best way to support my open-source projects is by becoming a Comfy Sponsor on GitHub!

https://github.com/sponsors/instafluff

Come and hang out with us at the Comfiest Corner on Twitch!

https://twitch.tv/instafluff

Instructions

How to configure your project to use these ESLint settings.

TypeScript

To set up ESLint with this configuration in your TypeScript project, you can follow these steps:

  1. Install the necessary dev dependencies along with ComfyCase:
npm install --save-dev eslint @typescript-eslint/parser @typescript-eslint/eslint-plugin eslint-config-comfycase
  1. Create an .eslintrc.json file in the root of your project and define your configuration rules, extending from ComfyCase:
{
  "env": {
    "node": true,
    "es6": true
  },
  "extends": [ "eslint:recommended", "comfycase" ],
  "parser": "@typescript-eslint/parser",
  "parserOptions": {
    "ecmaVersion": 2018,
    "sourceType": "module"
  },
  "plugins": ["@typescript-eslint", "node"],
  "rules": {
    // your configuration rules go here
  }
}
  1. Add a script to your package.json file to run ESLint on your project:
{
  "scripts": {
    "lint": "eslint . --ext .js,.ts"
  }
}
  1. You can then run the lint script with npm run lint or automatically fix them with npm run lint -- --fix.

JavaScript

To setup ESLint with this configuration in your JavaScript project, you can follow these steps:

  1. Install the necessary dev dependencies:
npm install --save-dev eslint eslint-config-comfycase
  1. Create an .eslintrc.json file in the root of your project and define your configuration rules:
{
  "env": {
    "node": true,
    "es6": true
  },
  "extends": [ "eslint:recommended", "comfycase" ],
  "parserOptions": {
    "ecmaVersion": 2018,
    "sourceType": "module"
  },
  "rules": {
    // your configuration rules go here
  }
}
  1. Add a script to your package.json file to run ESLint on your project:
{
  "scripts": {
    "lint": "eslint . --ext .js"
  }
}
  1. You can then run the lint script with npm run lint or automatically fix them with npm run lint -- --fix.