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

v5.0.1

Published

Yet Another ESLint Config. This one installs rules required to use standardJS with Gatsby projects

Downloads

1,590

Readme

Gatsby Standard - ESLint Config

Easily Lint your Gatsby site projects for StandardJS.

JavaScript Style Guide npm npm

ESLint rule configuration for Gatsby Sites. This rule set is designed to closely match the Gatsby Starters while still following StandardJS. Simply install and extend to clean up your GatsbyJS code! The plugins and parser used are dependencies of this project. No need to specify them separately in your project.

This config is designed to be used in conjunction with prettier for automatic code formatting. Conflicting rules have been disabled through eslint-config-prettier. See the "Use With Atom" section below for a suggestion on how to implement this config with prettier for automatic linting and formatting.

@babel/eslint-parser is included to support new JavaScript features used in advanced Gatsby projects.

Usage

Install the configs by running:

npm install --save-dev eslint  eslint-config-gatsby-standard

Then simply create a .eslintrc.json at your project root:

{
  "extends": "gatsby-standard"
}

Be sure you also have an .eslintignore file in your project root so you won't receive unnecessary lint errors from Gatsby:

public
static
.cache
content

Plugins Used:

Use With Atom

To use with prettier just add the .prettierrc.json config file to the root of the project:

{
  "semi": false,
  "singleQuote": true,
  "trailingComma": "es5"
}

If you use Atom, you can install linter-eslint to view the results of Gatsby Standard immediately.

apm install linter-eslint

Disable "Fix errors on save" and install prettier-atom:

apm install prettier-atom

Choose "ESLint Integration" in the package settings. This will use a global install of prettier-eslint but it will still follow the Gatsby Standard linting rules.

Be sure to check "Run Prettier Last" and optionally "Format Files on Save" and "Show in Status Bar." Most other code editors have similar packages to format on demand.

License

MIT © 2021 Brandon Kalinowski