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

v3.0.0

Published

ESLint configs for Open Government Products

Downloads

1,392

Readme

eslint-config-opengovsg

Goal

The goal of this package is to provide reasonable defaults for most common scenarios, so that developers can start building without worrying about linting configurations.

Explanation

ESLint is a tool to "find and fix problems in your JavaScript code" (from https://eslint.org/). We use ESLint to help us write better code. However, we do not want to invest efforts into the fine-tuning of detailed configurations, as those efforts can be better invested into building other things.

As a result, we will NEVER have self-defined opinions in the library, which means rules section should not exist in the configs. Instead, only recommended rule sets from the biggest linting libraries (e.g. eslint:recommended) will be used. Essentially:

  1. We fully trust the community out there to maintain a reasonable set of recommended rules, so that most common error-prone patterns are covered
  2. When something really does not make sense in recommended, there are 2 options:
    • influence and change the upstream recommended rule set
    • or do overrides in .eslintrc in our own repositories, NOT here. If a rule does not make sense to the broader community thus cannot enter the recommended rule set, it would not make sense to be here either.

Usage

To install (including all the peer dependencies as devDependencies):

npx install-peerdeps --dev eslint-config-opengovsg

Depending on the usage, put one of the following into .eslintrc:

  • TypeScript (yep we use TypeScript by default in OGP: {"extends": ["opengovsg"]})
  • React ({"extends": ["opengovsg", "opengovsg/react"]} or {"extends": ["opengovsg/javascript", "opengovsg/react"]})
  • Pulumi ({"extends": ["opengovsg", "opengovsg/pulumi"]})
  • JavaScript (in case you really do not need TypeScript: {"extends": ["opengovsg/javascript"]})