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

v2.0.73

Published

Expensify's ESLint configuration following our style guide

Downloads

14,365

Readme

eslint-config-expensify

npm version

This package provides Expensify's .eslintrc as an extensible shared config. Most of our rules are based on Airbnb's style guide.

How to Develop

  1. You only need to make a PR with the changes. There is no need to bump the version in package.json file in your PR. A github action will automatically bump the version and publish the package to npm after PR is merged.

Testing

After you have submitted a PR,

  1. Get the full commitID of the last commit in your PR, and run npm install git+https://github.com/Expensify/eslint-config-expensify.git#COMMIT_ID in the repo against which you want to test those changes.
  2. This should update the resolved path of eslint-config-expensify in package-lock.json file, and ensures the repo is referencing to the correct local version of the eslint config.
  3. Now, you can run npm run lint or perform any other tests you want in that repo.

After PR is merged

  1. A GitHub action will automatically bump the version and publish the package to npm after PR is merged.
  2. Go into the App, Web-Expensify and Web-Secure repos and run npm install eslint-config-expensify@latest. This should update the package.json and package-lock.json file, and you can submit a PR with those changes.

Note as of now we have no way of testing these PRs without a separate App, Web or Web Secure PR

Usage

We export two ESLint configurations for your usage.

eslint-config-expensify

Our default export contains all of our ESLint rules, including ECMAScript 6+ and React. It requires eslint, eslint-plugin-import, eslint-plugin-react, and eslint-plugin-jsx-a11y.

Just add extends: 'expensify' to the .eslintrc file in the root directory of your project.

eslint-config-expensify/legacy

Just add extends: 'expensify/legacy' to the .eslintrc file in the root directory of your project.

Style Guide

Feel free to also check out our Javascript style guide, our general language-agnostic coding standards, and the ESlint config docs for more information.