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

@semi-solid/solid

v0.1.1

Published

SolidJS runtime layer for Semi-Solid. Sits between the zero-dependency stubs in `@semi-solid/runtime` and your components, providing reactive implementations that depend on `solid-js`.

Readme

@semi-solid/solid

SolidJS runtime layer for Semi-Solid. Sits between the zero-dependency stubs in @semi-solid/runtime and your components, providing reactive implementations that depend on solid-js.

Install

pnpm add @semi-solid/solid

solid-js ^1.9.0 is a peer dependency — install it alongside this package.

What's inside

| Export | Source | Description | |--------|--------|-------------| | tap, tapWhen, tapRemote, tapPersonalized, liquidRaw, blockAttrs | re-exported from @semi-solid/runtime | Compile-time stubs — the compiler replaces these with Liquid output and reactive signals | | t, setTranslations | re-exported from @semi-solid/runtime | i18n translation helper | | createTapSignal, __setSectionId | tapWhen.ts | Reactive signal that re-fetches from a Shopify data section when dependencies change | | __tapRemoteHtml | tapRemote.ts | Fetches rendered section HTML from another route via the Section Rendering API | | createPersonalizedSignal, __setPersonalizationBaseUrl, buildUrl | tapPersonalized.ts | Fetches personalized data from an external API with prefetch support | | createStore | store.ts | localStorage-backed reactive store (wishlists, recently viewed, etc.) |

Usage

Components never import from this package directly. They use the $lib/ Vite alias, which resolves to packages/solid/src/:

// src/snippets/ProductCard.tsx
import { tap } from '$lib/runtime';
import { t } from '$lib/i18n';

const title = tap('{{ product.title }}', 'Product');

The compiler transforms tap() / tapWhen() / tapPersonalized() calls at build time. The reactive implementations (createTapSignal, createPersonalizedSignal, etc.) are auto-imported by the compiler into the cleaned output — you don't call them yourself.

createStore

createStore is the one export you use directly in component code:

import { createStore } from '$lib/runtime';

const recentlyViewed = createStore<Product>('recently-viewed', { maxItems: 10 });

// Read
const items = recentlyViewed.items(); // Accessor<Product[]>

// Write
recentlyViewed.add(product);    // prepends, deduplicates, persists to localStorage
recentlyViewed.remove(product); // removes by JSON equality
recentlyViewed.clear();         // empties the store

Architecture

@semi-solid/runtime   (zero dependencies — stubs + types)
       |
@semi-solid/solid     (solid-js — reactive implementations)
       |
  Components          (import via $lib/ alias)
       |
@semi-solid/compiler  (Vite plugin — transforms source at build time)

The compiler emits $lib/runtime and $lib/tapWhen imports in the transformed output. The $lib alias in vite.config.ts points to packages/solid/src/, so Vite resolves everything without any component files needing to know the physical path.

Development

# Run tests
pnpm test

# Watch mode
pnpm test:watch