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

v2.1.0

Published

Shared ESLint config we use for React projects at b8ta.

Downloads

5

Readme

eslint-config-b8ta

Sharable ESlint config files to "extends" in our projects. Do not extend the files from the "rules" folder directly.

Configure Webpack Resolver for eslint-plugin-import

In projects that use special webpack resolve rules (such as resolve.alias), you will need to provide webpack config to allow eslint-plugin-import to resolve modules that it lints correctly.

1. Install eslint-import-resolver-webpack

yarn add -D eslint-import-resolver-webpack

Not every project needs this, so it is the consumer project's responsibility to manage the dependency. Recent working version tested was [email protected].

2. Update Settings of the project .eslintrc with import/resolver

{
  ...
  "settings": {
    "import/resolver": {
      "webpack": {
        "config": "./config/webpack.config.js"
      }
    }
  },
  ...
}

ESLint will find the config file using the path relative to the location of your package.json. If you want more power (e.g. using different webpack config for different builds), consider using Javascript eslint config.