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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@additionapps/eslint-config-addition

v2.2.0

Published

ESLint and Prettier config for Addition development.

Readme

ESLint Configuration for Addition

This project defines the ESLint and Prettier configuration for Addition development. It is published as a public npm package allowing other Addition projects to install it, so that the rulesets are shared between all projects and defined in one place. Currently the configuration is intended for linting Typescript React projects. The Javascript Standard ruleset is used rather than Google or AirBnB.

How to install in your Addition project

Install ESLint and supporting packages:

npm i -D eslint eslint-config-standard eslint-plugin-import eslint-plugin-node eslint-plugin-promise eslint-plugin-react eslint-plugin-standard "@typescript-eslint/eslint-plugin" "@typescript-eslint/parser" prettier eslint-config-prettier eslint-plugin-prettier

Then install the Addition ESLint config package:

npm install @additionapps/eslint-config-addition

Note the postinstall script will copy an .eslintrc.js file into the root of your current project.

Manually running the linter

In your project root:

npx eslint **/*.ts[x] --fix

Errors that can be fixed automatically will be, remaining errors will be listed.

Updating the package

If there is an update to the linting rules for Addition a new version of the package will be published. To update the package for use in a project:

npm update @additionapps/eslint-config-addition

Updating the linting rules

If you want to change the ESLint configuration update the current configuration in index.js. To update a Prettier rule, update the configuration in index.js and in .prettierrc.js.

Once the required rule changes have been made, update the package version number in package.json.

Then commit and push the changes to the Bitbucket repo (master branch).

Then: npm publish

Configuring IDEs to use your ESLint configuration

The IDEs will automatically detect the .eslintrc.js file in the project root.

PhpStorm

  1. Open Preferences
  2. Navigate to Languages and Frameworks | JavaScript | ESLint
  3. Select Automatic ESLint configuration option

For more details see https://www.jetbrains.com/help/phpstorm/eslint.html

VSCode

  1. If not already installed, Cmd + Shift + x and search for ESLint, then install it

  2. Open ESLint settings and click 'Configure Extension Settings'. (Click the cog icon next to the ESLint extension.)

  3. Click an 'Edit in settings.json' link and add the following to the file

    "eslint.validate": [
      "javascript",
      "javascriptreact",
      "typescript",
      "typescriptreact"
    ]

    This tells VSCode to lint Typescript files, not just JS.

  4. Set the remaining settings as desired. E.g. Tick 'Auto Fix On Save'