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

@lutaml/opal-runtime

v1.0.1

Published

Pure Opal runtime for browser and Node.js. Shared by @unitsml/unitsml and other Opal-compiled gems so they don't each ship their own Opal runtime.

Downloads

257

Readme

@lutaml/opal-runtime

Pure Opal runtime, extracted from a real Opal compile. Shared by @unitsml/unitsml and other Opal-compiled gems so a single Opal global exists across the dependency tree.

Why

Every Opal-compiled gem ships a copy of the Opal runtime. If a user installs two of them and loads both, two Opal globals fight for the same name — silent memory bloat in Node, undefined behavior in browsers.

A shared runtime package fixes this: each compiled gem declares @lutaml/opal-runtime as a peer dep, every consumer gets one Opal instance.

Usage (consumer)

// In an Opal-compiled gem's package.json
"peerDependencies": {
  "@lutaml/opal-runtime": "^1.0.0"
},
"peerDependenciesMeta": {
  "@lutaml/opal-runtime": { "optional": true }
}

The peer is optional: if absent, a self-contained bundle (with embedded Opal) still works for CDN users. Bundler users with shared runtime get the smaller external flavor.

Build

scripts/build.js runs Opal::Builder.build("opal/runtime-stub") and writes the resulting JS to dist/runtime.js. Single source of truth — the runtime here is what @unitsml/unitsml compiles against.

Source of truth

Built from the latest released opal gem. Maintained by the lutaml org.