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

@dotcom-reliability-kit/eslint-config

v3.1.1

Published

A linting config, specifically focussed on enhancing code quality and proactively catching errors/bugs before they make it into production

Downloads

1,421

Readme

@dotcom-reliability-kit/eslint-config

A linting config, specifically focussed on enhancing code quality and proactively catching errors/bugs before they make it into production. This is not a replacement for the @financial-times/eslint-config-next, but it can be installed alongside it or as an extension in it's config. This module is part of FT.com Reliability Kit.

Usage

Install @dotcom-reliability-kit/eslint-config as a development dependency:

npm install --save-dev @dotcom-reliability-kit/eslint-config

Reference the shared configuration in your repository's own .eslintrc.js like so:

module.exports = {
extends: ['@dotcom-reliability-kit/eslint-config']
}

Avoid using .eslintrc file format (without a file extension), as this has been depracated.

Static Code Analysis

Add the following command to the scripts object in your repository's package.json:

"lint:js": "eslint ."

Run that command in your terminal to lint your files (either cd into the relevant directory or run from root). Any linting errors found by the config will be displayed in your terminal, with helpful suggestions on how to resolve them.

Migrating

Consult the Migration Guide if you're trying to migrate to a later major version of this package.

Contributing

See the central contributing guide for Reliability Kit.

License

Licensed under the MIT license.

Copyright © 2023, The Financial Times Ltd.