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

@sola-air-ui/core

v1.1.1

Published

Zero-VDOM reactivity engine — signals, effects, lifecycle, and intent primitives

Downloads

697

Readme

@sola-air-ui/core

Zero-VDOM reactivity engine for Sola AIR — signals, derived values, effects, component lifecycle, and the $intent primitive. This is the runtime that compiled .sola components import; most apps won't call it directly (use @sola-air-ui/compiler or the sola-air meta-package instead), but it's published standalone for anyone embedding Sola-compiled output in a custom build pipeline.

Install

npm install @sola-air-ui/core

What's in here

  • Signals — createSignal, createDerived, createEffect, flushSync
  • Lifecycle — onMount, onDestroy, pushContext/popContext (component-scoped mount/destroy queues)
  • Data & intent — createData, createIntent, configureIntent (ambient AI state resolution, with SSE streaming support)
  • IIFE build — @sola-air-ui/core/iife exports a pre-bundled dist/sola-core.iife.js for no-bundler environments (e.g. embedding in a CMS widget or a <script> tag), guarded so multiple copies on one page share a single instance via window.SolaCore.

Usage

Compiled .sola output imports these directly:

import { createSignal, createDerived, onMount } from '@sola-air-ui/core';

const [count, setCount] = createSignal(0);
const doubled = createDerived(() => count() * 2);

onMount(() => {
  console.log('mounted, doubled =', doubled());
});

Component lifecycle contract

pushContext() / popContext(ctx) scope onMount/onDestroy callbacks to one component instance. If your own runtime code manually mounts nested components, always flush a component's mounts/destroys with the specific context object pushContext() returned for it — not by relying on whichever context happens to be globally "active":

const ctx = pushContext();
onMount(() => { /* ... */ });
// ...build DOM, possibly mounting nested child components...
__flush_mounts(ctx);   // pass ctx explicitly

This matters because a mounted child component's own context stays on the stack (it isn't popped until that child unmounts), so relying on implicit "current" context after nested mounts silently drops the parent's own mount callbacks. @sola-air-ui/compiler-generated code already does this correctly.

License

MIT — see the repo root for the full license and changelog.