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-lapikit

v0.0.2

Published

Official ESLint configuration for [Lapikit](https://lapikit.dev) — prevents false positives caused by Lapikit's `<kit:*>` syntax and preprocessor.

Readme

eslint-config-lapikit

Official ESLint configuration for Lapikit — prevents false positives caused by Lapikit's <kit:*> syntax and preprocessor.

Why?

Lapikit uses a custom <kit:*> syntax that is transformed into standard Svelte components at build time. Some of these components rely on named snippets (like activator, indicator, etc.) that ESLint may incorrectly flag as unused variables.

This package configures ESLint to ignore these false positives so you can focus on writing code.

Requirements

  • ESLint >=9.0.0 (flat config)
  • @typescript-eslint/eslint-plugin >=6.0.0
  • lapikit >=0.5.0

Installation

npm install -D eslint-config-lapikit
pnpm add -D eslint-config-lapikit
yarn add -D eslint-config-lapikit
bun add -D eslint-config-lapikit

Usage

Add the config to your eslint.config.js:

import lapikitConfig from "eslint-config-lapikit";

export default [...lapikitConfig];

That's it! The config will automatically handle all Lapikit-specific false positives for .svelte files.

Handling Conflicts

eslint-config-lapikit configures the @typescript-eslint/no-unused-vars rule for Lapikit snippets. If you already have a custom configuration for this rule, place the Lapikit config first so your own rules take precedence:

import lapikitConfig from "eslint-config-lapikit";

export default [
  ...lapikitConfig, // always first
  {
    rules: {
      "@typescript-eslint/no-unused-vars": [
        "error",
        {
          // your custom options here
          varsIgnorePattern: "^myCustomPattern$",
        },
      ],
    },
  },
];

What's Included

This config applies the following rules to all **/*.svelte files:

| Rule | Configuration | | ----------------------------------- | -------------------------------------- | | @typescript-eslint/no-unused-vars | Ignores Lapikit reserved snippet names |

Ignored snippet names

The following snippet names are recognized as Lapikit reserved snippets and will not be flagged as unused:

  • activator
  • indicator
  • append
  • prepend
  • close
  • load
  • tooltip
  • prependInner,
  • appendInner

Known Limitations

This package only handles ESLint false positives. Your IDE may still show a ts(6133) warning for the same snippets — this is a separate issue with the TypeScript language server. See the documentation for more information.

License

Licensed under the MIT license.

Copyright © 2025 - 2026 Nycolaide