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

eslint-config-playvs

v3.0.1

Published

The official eslint configuration for PlayVS.

Readme

eslint-config-playvs

Take 2 minutes to absorb this readme.

Updating This Package

When dependencies go out of date, use yarn upgrade-interactive --latest and upgrade all of them. Then in package.json, (1) copy the dependencies to peerDependencies and (2) bump the version number. Next, commit your work and publish to master. Finally, run yarn publish--keep the new version number.

Installation

Run the following commands at the root of your project:

yarn add eslint-config-playvs
yarn add --dev @typescript-eslint/eslint-plugin eslint eslint-config-airbnb eslint-config-prettier eslint-plugin-import eslint-plugin-jest eslint-plugin-jsx-a11y eslint-plugin-prettier eslint-plugin-react prettier typescript

Then create the following files:

// filename: ./.eslintrc.js

module.exports = {
  env: {
    browser: true, // XXX: if your project runs in the browser
    jest: true, // XXX: if your project runs uses jest
    node: true, // XXX: if your project runs on node
  },
  extends: ['playvs'],
}
// filename: ./prettier.config.js

module.exports = require('eslint-config-playvs/prettier.config')

Add a linting script like the following to your package.json file:

"lint": "eslint src --ext js,jsx,ts,tsx",

Then run yarn lint and see what the results are. Find a file with linting errors and hit CMD+s. Does it lint and prettify the file? If not, you may have made a mistake.

Please correct any errors in these instructions.

Webpack Aliasing

If you'd like to add webpack aliasing make the following changes:

(for compilation)

// filename: ./webpack.config.js

...
  resolve: {
    ...
    alias: {
      Pages: path.resolve(__dirname, 'src/pages/'),
    },
    extensions: [...config.resolve.extensions, '.ts', '.tsx'],
  },
...

(for linting)

// filename: ./.eslintrc.js
  ...
  settings: {
    'import/resolver': {
      alias: {
        map: [['Pages', './src/pages']],
        extensions: ['.js', '.jsx', '.ts', '.tsx'],
      },
    },
  },
  ...

The result:

import { Home } from 'Pages'