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

v2.0.0

Published

My personal ESLint config

Downloads

100

Readme

eslint-config-bryanberger

This package provides my personal .eslintrc as an extensible shared config.

Usage

I export five ESLint configurations for your usage.

eslint-config-bryanberger

My default export contains most of my ESLint rules, including ECMAScript 6+, TypeScript and React. It requires eslint, eslint-plugin-import, @stylistic/eslint-plugin, @typescript-eslint/eslint-plugin, @typescript-eslint/parser, eslint-import-resolver-typescript, eslint-plugin-react, eslint-plugin-react-hooks, and eslint-plugin-jsx-a11y.

Install the correct versions of each package

npx install-peerdeps --dev eslint-config-bryanberger

or

npm i -D eslint eslint-plugin-import @typescript-eslint/eslint-plugin @typescript-eslint/parser eslint-import-resolver-typescript eslint-plugin-react eslint-plugin-react-hooks eslint-plugin-jsx-a11y @stylistic/eslint-plugin

or with pnpm:

pnpm add -D eslint eslint-plugin-import @typescript-eslint/eslint-plugin @typescript-eslint/parser eslint-import-resolver-typescript eslint-plugin-react eslint-plugin-react-hooks eslint-plugin-jsx-a11y @stylistic/eslint-plugin

Extends config

Add "extends": "bryanberger" to your .eslintrc to extend the entire configuration.

If you only want to extend one of my configurations, your can only add "extends": "bryanberger/$CONFIG_NAME" to your .estlinrc. Here is the configurations list:

  • bryanberger/javascript
  • bryanberger/typescript
  • bryanberger/imports
  • bryanberger/react

You can extend multiple selected configs with the following syntax:

{
	"extends": [
		"bryanberger/javascript",
		"bryanberger/react"
	]
}