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-plugin-tribou

v2.0.1

Published

Start with JS Standard Style but push towards better readability, git-awareness, vim-usability, and React and ES6 best practices

Downloads

141

Readme

eslint-plugin-tribou

npm version CircleCI Project Status: Active - The project has reached a stable, usable state and is being actively developed.

Start with JS Standard Style but push towards better readability, git-awareness, vim-usability, and React and ES6 best practices.

Quick Start

NOTE: If you're migrating from eslint-config-tribou and want to maintain compatibility, see the Legacy Configuration.

npm install --save-dev \
    eslint-plugin-tribou \
    babel-eslint \
    eslint

Then add the following to your .eslintrc:

{
  "extends": [
    "plugin:tribou/recommended"
  ],
  "plugins": [
    "tribou"
  ]
}

Or add an .eslintrc.yml:

extends:
  - plugin:tribou/recommended

plugins:
  - tribou

# Wow, that was easier... 😉

Flow

By default, Flow typing is required for an entire project since eslint-plugin-flowtype will require the \\ @flow annotation to be set at the top of every file and subsequently check for all other flow annotation requirements in that file. This allows new projects to enforce Flow typing on every file from the start.

If you do not wish to use Flow typing on every file (or at all) in a project, this config can still enforce all of its other standards (including Flow linting on files that do have the // @flow annotation). To disable this "universal" Flow typing requirement in your .eslintrc:

{
  ...
  "settings": {
    "flowtype": {
      "onlyFilesWithFlowAnnotation": true
    }
  }
}

Or in your .eslintrc.yml:

...
settings:
  flowtype:
    onlyFilesWithFlowAnnotation: true

Prettier Usage

Like using prettier? You can ignore rules that affect prettier styles with eslint-config-prettier

Install:

npm install --save-dev eslint-config-prettier

And add the configs to your .eslintrc.yml:

extends:
  - plugin:tribou/recommended
  - prettier
  - prettier/flowtype
  - prettier/react

plugins:
  - tribou

Legacy Configuration

In order to apply the rules equivalent to eslint-config-tribou@^3.0.0, install v0.3.0 instead:

npm install --save-dev \
    eslint-plugin-tribou@^0.3.0 \
    babel-eslint@^8.0.0 \
    eslint@^4.0.0