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

@mtdt/observeops-ds-elements

v0.1.26

Published

ObserveOps design system as framework-agnostic Web Components (obs-*). The real DS components for React/Vue/HTML.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

niravbhatt1317niravbhatt1317

Keywords

observeopsdesign-systemweb-componentsmotadataobs

Readme

@mtdt/observeops-ds-elements

The real ObserveOps design-system components as framework-agnostic Web Components (obs-* custom elements). Use them in React, Vue, Svelte, Angular, or plain HTML — the output is the actual DS component, not a reconstruction, so it looks and behaves like the product.

This is the build target the AI Operating Contract points at: use these components, don't reconstruct them.

Install

npm install @mtdt/observeops-ds-elements @mtdt/observeops-ds-css

Import once to register every obs-* element (registration runs on import), and load the token CSS so colours theme correctly:

import '@mtdt/observeops-ds-elements'                       // registers obs-button, obs-tag, …
import '@mtdt/observeops-ds-css/dist/observeops-ds.css'     // the DS tokens (light + dark)

Then use them anywhere:

<obs-button variant="primary">Save</obs-button>
<obs-input type="search" placeholder="Search…"></obs-input>
<obs-tag variant="tag-green">Active</obs-tag>
<obs-severity severity="critical" display-text></obs-severity>
<obs-radio as-button options="Low,Medium,High" value="Medium"></obs-radio>
<obs-switch checked></obs-switch>

Dark theme: set data-theme="dark-theme" on <html> (every token is theme-aware).

The components (obs-*)

obs-button · obs-input · obs-select · obs-switch · obs-checkbox · obs-radio · obs-link · obs-tag · obs-severity · obs-tags · obs-tooltip · obs-date-time-picker · obs-filters · obs-selected-pills · plus the obs-layout-* foundation elements.

Props/variants: every component's full API (props, variants, states, tokens, and the decision-grade usage rules — which variant when) lives in the machine spec @mtdt/observeops-ds-spec, and via the MCP server @mtdt/observeops-ds-mcp (get_component, search_components, …). Read the contract in @mtdt/observeops-ds-spec/AGENTS.md before building.

Events

Vue-emitted events deliver the value in event.detail as an array — unwrap it:

el.addEventListener('change', e => { const value = Array.isArray(e.detail) ? e.detail[0] : e.detail })

Verify your render

Check that what you built matches the DS (tokens · components · variants · layout) with the shipped conformance checker: node node_modules/@mtdt/observeops-ds-spec/conformance/ds-conformance.mjs <your-page.html> (aim ≥ 90).