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

@intentic/extension-ui

v1.317.0

Published

The UI kit intentic extensions render with, host-provided at runtime (the app's own components via the import map), so extension UI is always native to the shell

Readme

extension-ui

The UI kit extensions render with: a curated slice of the editor's design system that the host supplies at runtime, so extension views use the shell's own component instances.

flowchart LR
    ui["_editor/ui<br/>design system"] -- "re-exported by src/" --> kit(["extension-ui"])
    kit -- "compiled into" --> host["Editor<br/>hostModules.ts"]
    bundle["Extension bundle"] -- "import map" --> shim["/ext-shims/extension-ui.js"]
    shim -- "globalThis.__intenticHost" --> host
  • src/index.ts re-exports chosen components and helpers from @intentic/ui (_editor/ui) plus the PrimeVue primitives extension views use. Nothing is reimplemented, so an extension view looks and behaves like the shell around it. This dependency on _editor/ui is a recorded exception to the _shared/ boundary.
  • At runtime the host supplies the kit: hostModules.ts publishes the editor's own module instances on globalThis.__intenticHost, and the import map in the editor's index.html resolves @intentic/extension-ui to a shim that reads them. A second copy would render unthemed, outside the app's reactivity and its query cache.
  • scripts/build.mjs compiles the published package from _editor/ui's sources: declarations pruned to what the kit re-exports, and a dist/index.js bridge that throws when loaded outside an intentic host.
  • names.mjs lists the runtime export names by hand, because the .vue graph cannot load in Node. The editor's shim generator reads it, and a dev-time assertion in hostModules.ts catches drift.
  • ./diff, ./format, ./i18n and ./worker skip the component barrel, for extension tests that run without a Vue compiler. ./worker is also what a worker module imports serveWorkerCall from. A worker has no host bridge, so an extension built outside this repository bundles that module into its worker instead of marking it external.

Key files

Commands

pnpm --filter @intentic/extension-ui build