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-codestates

v1.0.0

Published

An ESLint configuration enforcing Code States's style guide

Downloads

4

Readme

Enforcing Code States's Style Guide

This is an installable ESLint configuration file that enforces Code States's style guide.

ESLint is a tool for identifying and reporting on patterns found in JavaScript code, with the goal of making code more consistent and avoiding bugs. It's an invaluable tool when working with other engineers.

System Requirements

A working version of Node.js

Installation

Install ESLint globally by running the following command in your terminal:

npm install -g eslint

Install the Code States style guide configuration:

npm install -g codestates/eslint-config-codestates

Enforce the style guide in a project

Create an .eslintrc.js file in the root directory of your repository:

module.exports = {
  extend: 'codestates',
  rules: {
    // Rules here will override the 'codestates' configuration
    // http://eslint.org/docs/rules/
  }
};

Now, you can run ESLint from the command line:

eslint [options] [file|dir|glob]*

For example:

eslint someFile.js someOtherFile.js
eslint client/**

If you don't see any output, your files have passed all the linting rules. In addition to the command line interface, ESLint can be integrated into various build systems like Gulp, Grunt, or a pre-commit hook.

Enforce the style guide in Sublime Text

By downloading and configuring a couple of plugins for Sublime Text, you can receive live feedback about your code's syntax and style, much like spelling errors in a word document. This is a very useful practice to build muscle memory around good style habits.

Install SublimeLinter

The easiest way to download plugins for Sublime Text is through Package Control. With Package Control, you can install SublimeLinter and its ESLint plugin from the Command Palette (cmd + shift + p):

  • Package Control: Install Package -> SublimeLinter
  • Package Control: Install Package -> SublimeLinter-contrib-eslint

Configure SublimeLinter

Without any configuration, SublimeLinter will only enforce rules from a .eslintrc file. If no .eslintrc file exists among the open files, SublimeLinter will fall back to the default behavior the eslint command, and only enforce syntax errors.

You can configure SublimeLinter to enforce the Code States style guide on files/projects without an .eslintrc file.

Navigate to Preferences -> Package Settings -> SublimeLinter -> Settings - User and update the linters section to the following:

"eslint": {
  "@disable": false,
  "args": [
    "--config",
    "codestates"
  ],
  "excludes": []
}