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

@threadlabs/looma

v0.10.8

Published

Looma components as HTML, Vue, and plain DOM, with design tokens.

Readme

@threadlabs/looma

Looma's components, written once as Declarative HTML Components and shipped three ways: as HTML, as Vue components, and as plain DOM factories.

pnpm add @threadlabs/looma

Vue

import "@threadlabs/looma/tokens.css";
import "@threadlabs/looma/vue.css";
import { Button, TopBar } from "@threadlabs/looma/vue";

The Vue components are ordinary Vue 3.5 single-file components, compiled to JavaScript with declarations; the .vue sources ship beside them. They depend on Vue and Looma only.

The editor is Tiptap-based and needs @tiptap/vue-3@^2.11.5:

import { LoomaEditor } from "@threadlabs/looma/vue/editor";
import { getDefaultEditorExtensions } from "@threadlabs/looma/editor/extensions";

The editor components' event and geometry types, without Tiptap, are in @threadlabs/looma/editor/ui.

HTML

<link rel="stylesheet" href="…/@threadlabs/looma/tokens.css">
<script type="module">
  import "@threadlabs/looma";
</script>

<ui-stack gap="m">
  <ui-button variant="solid">Save</ui-button>
</ui-stack>

Importing the package registers every component with the HTML Next runtime, which turns each <ui-*> element into its native root. Each component's styles are scoped to it; the token stylesheet is the only stylesheet to include. Without a build, link components one by one from @threadlabs/looma/components/<tag>/<tag>.html.

Theming

Components read design tokens (--ui-* custom properties) from tokens.css and a theme (theme-light.css, theme-dark.css, theme-high-contrast.css), and each exposes its own --ui-<component>-* properties. Set them on the component or any ancestor.