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

@scayle/eslint-auto-explicit-import

v0.3.0

Published

Automatically add explicit imports to ESLint

Readme

@scayle/storefront-eslint-auto-explicit-import

An extension of the official @nuxt/eslint module to insert more explicit import statement automatically using eslint --fix into a Nuxt-based SCAYLE Storefront project.

NOTE: Currently composables, utilities, helper functions and imported functions from packages will be automatically inserted as imports. No components used within a <template> will be imported by it!

Example

Details

Usage

Add local module to nuxt.config.ts:

export default defineNuxtConfig({
  modules: [
    // Both are required
    '@nuxt/eslint',
    '@scayle/eslint-auto-explicit-import',
  ],
})

Followed by adding a dedicated eslint flat config if none exists:

// eslint.config.mjs
import withNuxt from './nuxt/eslint.config.mjs'

export default withNuxt({
  // Your ESLint config
})

Running eslint should now throw errors if a source file does use auto-import. Adding --fix allows for automatically inserting / fixing of missing imports.

# pnpm lint .
pnpm lint . --fix

Troubleshooting

  1. Should a Vue component not have a dedicated <script> tag with some content within, it might be possible that the included local eslint-plugin-unimport fails with a range undefined error. In this case it is necessary to manually add the missing <script> tag with some dummy content.