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

@quangit/eslint-config

v0.0.10

Published

ESLint rules that we use at CAR FOR YOU

Readme

CAR FOR YOU Eslint config

semantic-release

Usage

npm install @quangit/eslint-config

Add a lint script to package.json:

  "lint": "eslint --ext ts,js,tsx,jsx,json ."

Add a format script to package.json to be able to use auto fix:

  "format": "npm run lint -- --fix",

ESLint configuration

Create .eslintrc.js in the root of the project:

  module.exports = {
    extends: ["@quangit/eslint-config"],
  }

This package provides multiple eslint configurations. They build on top of one another so there's no need to include multiple ones.

  • If you're working on plain typescript project use the default:
    @quangit/eslint-config
  • If you're working on react project use:
    @quangit/eslint-config/react
  • For nextjs applications use:
    @quangit/eslint-config/next

Prettier configuration

Create .prettierrc.js in the root of the project:

module.exports = {
  ...require("@quangit/eslint-config/prettier"),
}

VSCode integration

ESlint

There's an official eslint plugin available to get notifications about linter errors.

Auto-fixing problems on save

You can add:

"editor.codeActionsOnSave": {
  "source.fixAll.eslint": true
}

to your settings.json to fix fixable eslint errors on file save. This will only fix things that can be auto-fixed. It also might take some time.

Prettier

There is a pretty good prettier formatter available. This will add prettier as an option to format document via command palette.

You can also set prettier as default formatter for javascript, typescript and react files. Just add:

"[typescript]": {
  "editor.defaultFormatter": "esbenp.prettier-vscode"
},
"[javascript]": {
  "editor.defaultFormatter": "esbenp.prettier-vscode"
},
"[javascriptreact]": {
  "editor.defaultFormatter": "esbenp.prettier-vscode"
},
"[typescriptreact]": {
  "editor.defaultFormatter": "esbenp.prettier-vscode"
}

to your settings.json.

Auto-formatting on save

You can enable formatting on save under Settings -> Text Editor -> Formatting.

Development

npm run build

You can link your local npm package to integrate it with any local project:

cd carforyou-eslint-config
npm run build

cd carforyou-listings-web
npm link ../carforyou-eslint-config

Release a new version

New versions are released on the ci using semantic-release as soon as you merge into master. Please make sure your merge commit message adheres to the corresponding conventions.

Circle CI

You will need to enable the repository in circle CI ui to be able to build it.

For slack notifications to work you will need to provide the token in circle settings.