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

@appenin/eslint-config

v0.0.5

Published

Appenin's ESLint config, following our styleguide

Readme

@appenin/eslint-config

Appenin's ESLint config with TypeScript and React support

Setup

1) Install

yarn add -D @appenin/eslint-config

For the backend, add:

yarn add -D [email protected] typescript @typescript-eslint/parser eslint-config-prettier prettier eslint-config-standard eslint-plugin-chai-friendly eslint-plugin-import eslint-plugin-simple-import-sort eslint-plugin-mocha eslint-plugin-node eslint-plugin-prettier eslint-plugin-promise eslint-plugin-standard

For the frontend, add:

yarn add -D [email protected] typescript @typescript-eslint/parser @typescript-eslint/eslint-plugin prettier eslint-config-prettier eslint-plugin-prettier eslint-config-next

2) Configure ESLint

Add "extends": ["@appenin/eslint-config"] to your ESLint config file.

If you need React support, add "extends": ["@appenin/eslint-config/next"] instead.

This config requires knowledge of your TypeScript config. In your ESLint config, set parserOptions.project to the path of your tsconfig.json.

An example .eslintrc:

{
  "extends": ["@appenin/eslint-config/next"]
}

3) Run ESLint

Open a terminal to the root of your project, and run the following command:

npx eslint . --ext .js,.jsx,.ts,.tsx

ESLint will lint all .js, .jsx, .ts, and .tsx files within the current folder, and output results to your terminal.

You can also get results in realtime inside most IDEs via a plugin.

4) Fix on save Eslint errors

JetBrains IDE (WebStorm, Intellij)

  1. JetBrains IDE already provide Eslint plugins.
  2. You just need to do to Preferences > Languages & Framework > Eslint and check run eslint --fix on save

VS Code

  1. Install EsLint plugins for VS Code
  2. Go to Preferences > edit settings.json
  3. Paste the following code:
{
  "editor.codeActionsOnSave": {
    "source.fixAll.eslint": true
  }
}