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

@build-chores/eslint-config-lint

v0.9.0

Published

Linting JS projects is complicated.

Downloads

12

Readme

@build-chores/eslint-config-lint

Linting JS projects is complicated.

Synopsis

License: GPL v3 npm version Build Status

Lint your JavaScript code. This config is based on Airbnb's base lint configuration and includes support for Prettier, the Flow type checker and promises.

Usage

Install the @build-chores/eslint-config-lint package into your project:

yarn install --dev @build-chores/eslint-config-lint

Create a .eslintrc file containing the following snippet. See the example .eslintrc for a template.

{
  "extends": ["@build-chores/lint"]
}

To use flow as well place a .flowconfig and .flowcoverage configuration file. See the example flowconfig and the example .flowcoverage for templates.

Note that even if flow isn't use an empty .flowconfig file has to be created.

This package installs flow-typed to install flow type definitions. To make it work in this setup the flow-libdefs wrapper script is provided. It takes the same arguments as flow-typed.

The following command installs type definitions for your dependencies.

yarn flow-libdefs install

Edit your package.json to include the following scripts. See the example package.json for a template.

{
  "scripts": {
    "fix": "yarn lint --fix",
    "flow:coverage": "yarn flow-coverage-report --config ./.flowcoverage",
    "flow:gen": "gen-flow-files --out-dir dist src",
    "flow:libdefs": "yarn flow-libdefs update",
    "lint": "eslint src/**/*.js**"
  }
}

Types are checked during the regular linting. If you want to run Flow separated, you can call the flow command directly with yarn flow.

See the rules file for details of the ESLint configuration.

You are ready to lint your JavaScript code.

Contribute

Check out our contributing.md to get started.

License