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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@guusje4525/eslint-plugin

v1.0.24

Published

Simple eslint plugin that checks if you are using the import wrong & if you are using inline functions

Readme

Eslint plugin

This eslint plugin adds 4 additional rules:

Check for wrong mui imports. In @mui/material or @mui/icons-material you should not use named imports. More info here

Wrong:

import { Box } from "@mui/material"

Correct:

import Box from "@mui/material/Box"

No inline functions in JSX are allowed. All logic should exists elsewhere, like a store.

Wrong:

const myComponent = <div>
    <button onClick={() => console.log('button was clicked')}>my button</button>
</div>

Correct:

const store = ....
const myComponent = <div>
    <button onClick={store.buttonClickHandler}>my button</button>
</div>

A map in JSX should contain a key

Wrong:

const myComponent = <div>
    {
        myArray.map(item => <h1>Hello, I am item</h1>)
    }
</div>

Correct:

const myComponent = <div>
    {
        myArray.map(item => <h1 key={item.id}>Hello, I am item</h1>)
    }
</div>

Every .go() query in electrodb should contain the parameter 'pages'

Wrong:

await MyEntity.query.client({} as any).go()

Correct:

await MyEntity.query.client({} as any).go({ pages: 'all' })

Use correct store name (mobx)

Wrong:

const store = useAuthStore()
const store = useStore(sp => new AuthStore(sp))

Correct:

const authStore = useAuthStore()
const authStore = useStore(sp => new AuthStore(sp))

Your eslint config file should look something like this:

module.exports = {
   plugins: ['@guusje4525'],
   rules: {
      '@guusje4525/mui-import-checker': 'warn',
      '@guusje4525/no-inline-functions-in-jsx': 'warn',
      '@guusje4525/jsx-key': 'warn',
      '@guusje4525/go-method-should-have-pages': 'warn'
   },
}