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

@wix/origami-runtime

v0.20.6

Published

React runtime for Origami-generated component wrappers: context bindings, providers, and className resolution

Readme

Origami runtime

Before local builds or tests, run pnpm -r run build from the repository root to build workspace dependencies in order.

The root entry exports binding, provider, and component authoring helpers.

svg(url, uri) creates a deferred SVG source without calling hooks or fetching content:

import { svg } from '@wix/origami-runtime'

<SvgImage svgId={svg(url, uri)} />

The existing withOrigami wrapper resolves these sources before rendering the original component, including sources nested in objects, arrays, and elementProps. Sources can be created inside repeater render callbacks. The wrapper uses a fixed set of hooks even when the number of sources changes. React elements and render callbacks are left intact; their own wrapped components resolve their sources.

Resolution returns only {svgContent}. The root SVG markup contains the calculated viewBox; nested SVG viewports remain unchanged. The viewport follows Thunderbolt: non-UGC artwork prefers data-bbox; UGC preserves the raw viewport or falls back to width and height. The UGC fallback accepts unitless and pixel dimensions; other units leave the viewport unspecified.

Sources receive plain URL and URI strings and have no dependency on the media SDK. DM reconstructs the Core vector from the expression without fetching or executing it. The wrapper supplies empty SVG content while loading or after a fetch failure, reuses loaded URLs within its mounted instance, and cancels pending requests when its source URLs change or it unmounts. The existing useSvgProps(url, uri) hook uses the same resolution implementation for direct hook consumers; it must be called at the top level of a React component or hook.

Layout components and the shared DOM/CSS contract belong to @wix/origami-system-components. This package has no layout subpaths or system-components dependency.