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

@mundorum/oid

v0.3.1

Published

Web components based on the Digital Content Component (DCC) model for the Mundorum space.

Readme

-o-id

Web components based on the Digital Content Component (DCC) model for the Mundorum space.

Environment Install

In this project root directory:

npm install

Development

To bundle the JavaScript components and infrastructure, we adopt Vite. The following statements build the development and production packages:

Development Package

npm run build:dev

Production Package

npm run build

Playground and Test Environment

The environment can be prepared for local execution for learning, tests, and development. We suggest the following steps to prepare the environment:

To provide flexibility, the default package.json configuration does not include the -o-id library, and there are two installation options. They are exclusive, and you cannot apply both:

-o-id Adopter

If you are only using the -o-id library without modifying it, you can install it:

npm install @mundorum/oid

-o-id Developer

Suppose you are modifying the library and you want your modifications to reflect in the playground or test environment automatically. In that case, you can emulate the -o-id library installation as a node module straight from your dist directory.

There are two steps to link local Mundorum libraries in the development mode.

Inside /dist directory:

npm link

Inside /playground/npm/node_modules/ directory:

npm link @mundorum/oid

This procedure mimics the -o-id library installed in the npm straight from dist.

Development Server

If you wish to run tests in code developed under the -o-id framework:

Local Library Perspective

If you want to load NPM libraries locally, run the Vite server:

npm run dev

CDN Library Perspective

If you want to load libraries from the jsDelivr CDN, as it will be in the deployed version, you can run a local web server under VSCode, the plugin Microsoft Live Preview.