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

v2.6.9

Published

ESLint and Prettier configuration for NodeJS and/or ReactJS projects, either Javascript and/or Typescript based

Downloads

684

Readme

ESLint config xs

This package provides an opinionated ESLint and Prettier configuration for NodeJS and/or ReactJS (and possibly Tailwind) projects, either Javascript and/or Typescript based.

Rules

The following rules are explicitly applied on top of the base configuration exported from plugins:

  • "no-console": "off": node may use the native console.log and console.error without using 3rd party logging libraries
  • "import/order": "error": for improved readability
  • "singleQuote": true: for improved readability
  • "printWidth": 120: for improved readability, assuming a professional developer uses >= 21" display

You should provide in the root of your project:

  • .prettierrc (not mandatory)
  • tsconfig.json (mandatory)
  • tailwind.config.(js|cjs|mjs) (not mandatory)

If your tailwind config is not in the root of the project (eg: you are in a monorepo with pnpm) then provide the tailwind config path explicitly to eslint-config-xs with an env named ESLINT_XS_TW:

ESLINT_XS_TW=./packages/webapp/tailwind.config.ts pnpm eslint ./packages

Usage

Install:

yarn add --dev eslint-config-xs

Create a .eslintrc:

{
  "extends": ["eslint-config-xs"]
}

Extend as needed in your .eslintrc:

{
  "extends": ["eslint-config-xs"],
  "...my other rules..": ["..."]
}

Lint and fix:

yarn eslint --fix .