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

@loomidev/tag

v0.3.0

Published

<loomi-tag>/<loomi-tags> — themeable labels/badges, faint or dark, closable, selectable.

Readme

@loomidev/tag

<loomi-tag> — a themeable label/badge for grouping items or showing status. Faint or dark shade, optional outline, rounded, tiny, and a close button. Group several in <loomi-tags> to make them selectable, like a fancier checkbox group.

npm install @loomidev/tag lit
import "@loomidev/tag";

Basic Usage

<loomi-tag label="pending"></loomi-tag>

Light, Faint, and Dark Shades

Tags default to a faint tint. Set shade="light" for a paler chip with a border one shade stronger than the tag color, or shade="dark" for a deeper solid fill.

<loomi-tag label="pending" color="success" shade="light"></loomi-tag>
<loomi-tag label="pending" color="success"></loomi-tag>
<loomi-tag label="pending" color="success" shade="dark"></loomi-tag>

Common semantic colors: primary secondary info success error warning gray.

With Close Icons

Useful for removable selections, like a list of chosen filters. The tag removes itself from the DOM on click by default.

<loomi-tag label="pending" can-close></loomi-tag>
<loomi-tag label="pending" can-close color="warning"></loomi-tag>

Intercept the removal by listening for the cancelable close event:

document.querySelector("loomi-tag").addEventListener("close", (e) => {
  e.preventDefault(); // stop it from removing itself
  console.log("user wants to remove this tag — confirm first?");
});

Tiny Tags

Handy as a small hint next to a menu item — e.g. flagging what's new.

<loomi-tag label="just added" tiny color="success"></loomi-tag>
<loomi-tag label="new" tiny color="warning" shade="dark"></loomi-tag>

Rounded Tags

<loomi-tag label="pending" rounded></loomi-tag>
<loomi-tag label="pending" can-close rounded color="warning"></loomi-tag>

Outline Tags

No background fill — just a border in color. The shade still affects how light or dark the outline is.

<loomi-tag label="pending" outline color="warning"></loomi-tag>
<loomi-tag label="pending" can-close outline color="warning" shade="dark"></loomi-tag>

Selectable Tags

Wrap tags in <loomi-tags name="..."> to use them as a form control, similar to a checkbox group — give each <loomi-tag> a value, and the parent submits the selected values (comma-joined) under name.

<loomi-tags name="stack" color="warning" max="3">
  <loomi-tag label="laravel" value="laravel"></loomi-tag>
  <loomi-tag label="javascript" value="js"></loomi-tag>
  <loomi-tag label="node js" value="node"></loomi-tag>
  <loomi-tag label="tailwindcss" value="tailwind"></loomi-tag>
</loomi-tags>

Pre-Selected Values

<loomi-tags name="fridays" color="error" selected-value="hangout,sleep">
  <loomi-tag label="hangout with friends" value="hangout"></loomi-tag>
  <loomi-tag label="watch movies" value="movies"></loomi-tag>
  <loomi-tag label="sleeeeep" value="sleep"></loomi-tag>
</loomi-tags>

Reacting to Selection

document.querySelector("loomi-tags").addEventListener("change", (e) => {
  console.log(e.detail.values); // ["hangout", "sleep"]
});

Accessibility

For the library-wide baseline, see Foundations — Accessibility.

Responsive behavior

For the shared container and viewport rules, see Foundations — Responsive behavior.

Dark mode

For theme activation, token overrides, and contrast guidance, see Foundations — Dark mode.

Attributes

<loomi-tag>

| Attribute | Default | Description | | ------------- | --------- | ------------------------------------------- | | label | (blank) | Tag text (or use the default slot). | | color | primary | Any loomi color. | | shade | faint | light | faint | dark | | outline | false | Outline only, no fill. (boolean) | | rounded | false | Fully rounded. (boolean) | | tiny | false | Tiny size. (boolean) | | uppercasing | false | Uppercase the text. (boolean) | | can-close | false | Show a close button. (boolean) | | value | (blank) | Submitted value when inside <loomi-tags>. |

<loomi-tags> (selectable group)

| Attribute | Default | Description | | ---------------- | --------- | ------------------------------------------ | | name | (blank) | Submitted with the form. | | max | (blank) | Max selectable tags (no limit by default). | | selected-value | (blank) | Comma-separated values to pre-select. | | required | false | Marks the field required. (boolean) |

Slots

| Slot | Description | | ----------- | ------------------------------------ | | (default) | Content placed inside the component. |

Events

| Event | Description | | ----------------- | --------------------------------------------- | | change | Fired when the value is committed or changed. | | close | Fired when the component closes. | | loomi-tag-click | Fired when a tag is activated. |

Full Example

<loomi-tags name="stack" color="warning" max="3" required>
  <loomi-tag label="accounting" value="accounting" can-close rounded outline shade="dark"></loomi-tag>
  <loomi-tag label="marketing" value="marketing"></loomi-tag>
  <loomi-tag label="tech" value="tech"></loomi-tag>
</loomi-tags>

Framework integration

<loomi-tag> and <loomi-tags> are standard custom elements, so the browser can use them in plain HTML, Blade, React, Vue, Angular, Svelte, Astro, and most other frameworks. The important beginner rule is: install the package, import it once before the tag is rendered, then write the Loomi tag in your template.

Where to run commands

Run install commands from the app where you want to use this component. That means the folder that contains that app's package.json. Do not run these install commands from packages/tag unless you are editing LoomiUI itself.

cd /path/to/your-app
npm install @loomidev/tag lit

If you are contributing to LoomiUI itself, first move to the top-level components folder. That is where the main package.json for all packages lives, and pnpm --filter ... commands should be run from there:

cd /path/to/your-copy-of-loomiui/components
pnpm --filter @loomidev/tag build
pnpm --filter @loomidev/tag typecheck

Choose your framework

Use the CDN version for prototypes, documentation pages, or a quick reproduction. The import map tells the browser where to find Lit, which Loomi components use internally.

<script type="importmap">
  { "imports": { "lit": "https://esm.sh/[email protected]", "lit/": "https://esm.sh/[email protected]/" } }
</script>
<script type="module" src="https://esm.sh/@loomidev/tag"></script>

<loomi-tags>
  <loomi-tag color="success" label="Active"></loomi-tag>
  <loomi-tag color="warning" outline>Pending review</loomi-tag>
</loomi-tags>

In Vite, Webpack, Parcel, Rollup, or a framework build pipeline, install the package and import it once in your main app JavaScript file. After that, you can use the Loomi tag anywhere in your app.

import "@loomidev/tag";

Run the install command from your Laravel project root, then import the component in resources/js/app.js. If your project uses Laravel Vite, npm run dev and npm run build should also be run from the Laravel project root.

cd /path/to/your-laravel-app
npm install @loomidev/tag lit
npm run dev
// resources/js/app.js
import "@loomidev/tag";
<loomi-tags>
  <loomi-tag color="success" label="Active"></loomi-tag>
  <loomi-tag color="warning" outline>Pending review</loomi-tag>
</loomi-tags>

React can render Loomi tags directly. If you are on React 18, or if you need to pass arrays, objects, or functions, use a ref and assign those values after the component mounts.

import "@loomidev/tag";

export function LoomiExample() {
  return (
    <loomi-tags>
      <loomi-tag color="success" label="Active"></loomi-tag>
      <loomi-tag color="warning" outline>Pending review</loomi-tag>
    </loomi-tags>
  );
}

If TypeScript does not recognize the Loomi tag in JSX, add it to your app's JSX type declarations.

Import the package in the component that uses it, or once in your main Vue file. Vue templates can use Loomi tags directly. For arrays, objects, or functions, pass the value as a JavaScript property instead of as plain text.

<script setup>
import "@loomidev/tag";
</script>

<template>
  <loomi-tags>
    <loomi-tag color="success" label="Active"></loomi-tag>
    <loomi-tag color="warning" outline>Pending review</loomi-tag>
  </loomi-tags>
</template>

If Vue warns that the tag is an unknown component, configure compilerOptions.isCustomElement for tags that start with loomi- in your Vite or Vue config.

Import the package once and tell Angular to allow custom HTML tags with CUSTOM_ELEMENTS_SCHEMA. For NgModule apps, add the schema to the module instead of the standalone component.

// app.component.ts
import { CUSTOM_ELEMENTS_SCHEMA, Component } from "@angular/core";
import "@loomidev/tag";

@Component({
  selector: "app-root",
  standalone: true,
  schemas: [CUSTOM_ELEMENTS_SCHEMA],
  template: `
    <loomi-tags>
      <loomi-tag color="success" label="Active"></loomi-tag>
      <loomi-tag color="warning" outline>Pending review</loomi-tag>
    </loomi-tags>
  `,
})
export class AppComponent {}

Svelte can import the package inside a component script. Astro can import it in the frontmatter of the page or layout where the tag appears.

<script>
  import "@loomidev/tag";
</script>

<loomi-tags>
  <loomi-tag color="success" label="Active"></loomi-tag>
  <loomi-tag color="warning" outline>Pending review</loomi-tag>
</loomi-tags>
---
import "@loomidev/tag";
---

<loomi-tags>
  <loomi-tag color="success" label="Active"></loomi-tag>
  <loomi-tag color="warning" outline>Pending review</loomi-tag>
</loomi-tags>

Server-side rendering notes

Frameworks such as Next.js, Nuxt, SvelteKit, and Astro sometimes render HTML on the server before browser-only code runs. If your framework complains, move the Loomi import to client-side code. In Next.js, that usually means a component with "use client"; in Nuxt, it often means a .client.ts plugin.

Dependencies

  • @loomidev/core
  • @loomidev/icon