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

@hyperfixi/intent-element

v2.5.0

Published

<lse-intent> custom element — validates LSE protocol JSON and executes it via the hyperfixi runtime.

Readme

@hyperfixi/intent-element

The <lse-intent> custom element for hyperfixi — a declarative way to run LSE protocol JSON (LokaScript Explicit Syntax) from HTML. The element validates the JSON against the LSE schema, then executes it through the hyperfixi runtime.

Install

npm install @hyperfixi/intent-element

@hyperfixi/core is an optional peer dependency: validation works without it, but executing an intent needs the runtime (window.hyperfixi.evalLSENode).

Usage

The browser build auto-registers <lse-intent>:

<script src="hyperfixi.js"></script>
<script src="intent-element.iife.global.js"></script>

<!-- Inline LSE JSON -->
<lse-intent trigger="click">
  <script type="application/lse+json">
    {
      "action": "toggle",
      "roles": { "patient": { "type": "selector", "value": ".active" } }
    }
  </script>
  <button>Toggle</button>
</lse-intent>

<!-- …or fetch the intent from a URL -->
<lse-intent src="/intents/toggle.json"></lse-intent>

The intent is read from a child <script type="application/lse+json"> or fetched via the src attribute. The optional trigger attribute names the DOM event that runs the intent (default: run on connect).

Why a custom element

  • Declarative. Behavior travels as data — LSE JSON — not imperative code. It can be authored, stored, and served like any other content.
  • Validated. The JSON is checked against the LSE schema (via the zero-dependency @lokascript/intent package) before anything executes; malformed intents fail loudly instead of silently misbehaving.
  • Sandboxed. Execution runs through a bounded sandbox with a timeout, so a runaway intent can't lock the page.
  • Composable. Because the element accepts src="/intents/foo.json", intents can live in static files or come from an API.

API exports

For programmatic use (e.g. registering the element yourself, or custom schemas):

  • LSEIntentElement — the HTMLElement subclass (already defined as lse-intent by the browser build).
  • intentRegistry — the LSE command-schema registry.
  • Type: SandboxResult.

The IIFE build exposes these on window.HyperFixiIntentElement.

License

MIT