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

@lamiaoy/eslint-config

v3.0.0

Published

ESLint base config for Lamia projects

Downloads

115

Readme

@lamiaoy/eslint-config

Base ESLint config for Lamia projects

Install

With npm do:

npm install -D @lamiaoy/eslint-config

Create a .eslintrc.js to your project root with the following contents:

module.exports = {
    extends: '@lamiaoy/eslint-config'
};

Make sure you don't have any existing configs (.eslintrc.js, .eslintrc.yml, .eslintrc.json or similar). If you do, first merge their configurations into the new .eslintrc.js, and remove them afterwards.

Assuming ESLint is configured correctly, it should automatically pick up the new config.

Usage

You can configure PhpStorm to show lint errors in the IDE.

You should also add a convenience command to your package.json

...
"scripts": {
    "lint": "npm run lint:js && npm run lint:css"
    "lint:js": "eslint src/",
    "lint:css": "..." // Some CSS linter
}
...

Run the command with

$ npm run lint

You can also add a prepush hook through husky

"scripts": {
    "prepush": "npm run lint"
}

This will lint your code before pushing to BitBucket.

Override config

You can add / remove rules and environment configs freely in .eslintrc.js.

module.exports = {
    extends: '@lamiaoy/eslint-config',
    env: {
        browser: true // Allow browser globals, such as 'window' and 'document'
    },
    rules: {
        'no-console': 'off' // Allow console.log -statements in your code
    }
};

You can see the full list of available rules here.