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

v1.0.2

Published

ESLint rules specific to Gatsby

Downloads

13,695

Readme

eslint-plugin-gatsby

Collection of eslint rules made specifically for Gatsby. This package is meant to be a plugin for eslint within Gatsby projects and is configurable just like other eslint rules and plugins.

Table of Contents

Installation

# Using npm
npm install --dev eslint-plugin-gatsby

# Using yarn
yarn add --dev eslint-plugin-gatsby

How to Use

Plugins

To add the plugin into your ESLint config, add the gatsby plugin into the plugins array.

JSON
{
  ...
  "plugins": ["gatsby"]
  ...
  // rest of ESLint config
}
JavaScript
module.exports = {
  ...
  plugins: ['gatsby']
  ...
  // rest of ESLint config
}
YAML
...
plugins:
  - gatsby
...
# rest of ESLint config

Extends

This library has a default recommended config that your ESLint config can extend. To do so, add the line 'plugin:gatsby/recommended' to the extends array.

JSON
{
  ...
  "extends": ["plugin:gatsby/recommended"]
  ...
  // rest of ESLint config
}
JavaScript
module.exports = {
  ...
  extends: ['plugin:gatsby/recommended']
  ...
  // rest of ESLint config
}
YAML
...
extends:
  - 'plugin:gatsby/recommended'
...
# rest of ESLint config

Manually

In the case that you do not want to extend the recommended rules or you want to override some of the recommended rules, you can manually configure the rules within the object

JSON
{
  ...
  "rules": {
    "gatsby/use-gatsby-link": "warn" // set use-gastby-link to be an ESLint warning
  }
  ...
  // rest of ESLint config
}
JavaScript
module.exports = {
  ...
  'rules': {
    'gatsby/use-gatsby-link': 'warn' // set use-gastby-link to be an ESLint warning
  }
  ...
  // rest of ESLint config
}
YAML
...
rules: {
  'gatsby/use-gatsby-link': 'warn' # set use-gastby-link to be an ESLint warning
}
...
# rest of ESLint config

Motivation

I believe node projects should enforce code standards to hold developers to a certain set of rules that assist with keeping code consistent, safe, and structured well. I have worked on projects that used Gatsby and noticed a lack of eslint rules specific to gatsby conventions. Hence why this package was created. I wanted to be able to enforce the use of specific Gatsby conventions and components in code so that the code base is optimized best for the Gatsby framework.

Authors