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-lovely-code

v0.1.1

Published

Please, read before about [lovely-code collection](https://github.com/gustarus/lovely-code).

Readme

[Lovely code] Check my javascript with eslint

Please, read before about lovely-code collection.

What is included in standards?

Silver standard

The following tools are used for this standard in the configuration:

:floppy_disk:  Show current version of the configuration file.

Check browser compatibility with special features for eslint-plugin-compat

Use default configuration files for standards

1. Install browserlist lovely code package

yarn add browserslist-config-lovely-code --dev

2. Add browserslist section to your package.json

{
  "browserslist": [
    "extends browserslist-config-lovely-code/silver"
  ]
}

How to use?

How to install the presents?

1. Add via yarn package manager

yarn add lovely-code

How to use default configuration?

1. Define scripts command in your package.json

It would be better if you define only files which you want to test. For example: the following command will use custom configuration file and check only files with extension .js only in folder ./core.

{
  "scripts": {
    "lint:js": "./node_modules/.bin/eslint --config eslint-config-lovely-code/silver --ext .js ./core"
  }
}

2. Run the command

yarn lint:js 

How to extend from default configuration?

1. Create .eslintrc in the project

touch .eslintrc

2. Extend from the configuration and write your own rules

Open created file for editing and write your code.

{
  "extends": "lovely-code/silver",
  "rules": {
    "no-console": "error"
  }
}

3. Define scripts command in your package.json

{
  "scripts": {
    "lint:js": "./node_modules/.bin/eslint --ext .js ./core"
  }
}

2. Run the command

yarn lint:js 

Hints

How to resolve webpack aliases?

Specify path to your webpack configuration file (where the resolve property is defined).

{
  "extends": "lovely-code/silver",
  "settings": {
    "import/resolver": {
      "webpack": {
        "config": "./webpack/webpack.config.js"
      }
    }
  }
}

How to fix some of the errors?

Eslint have an ability to fix some of errors which were found. To use this feature run yarn run lint:js -- --fix. Or add this command to the package.json.

{
  "scripts": {
    "lint:js": "./node_modules/.bin/eslint --ext .js ./core"
  }
}

Or, if you already defined lint:js you can use the following syntax.

{
  "scripts": {
    "lint:js": "...",
    "lint:fix": "yarn lint:js --fix"
  }
}