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

@owcs/schemas

v0.1.11

Published

OWCS JSON Schema definitions and utilities

Readme

@owcs/schemas

JSON Schema definitions and validation utilities for OWCS (Open Web Component Specification).

Overview

This package provides:

  • JSON Schema definitions for OWCS specification versions
  • Schema validation utilities for validating OWCS files
  • Version management for schema evolution
  • TypeScript types for schema versions

The schemas define the structure of OWCS specifications including:

  • Component metadata (tagName, module, description)
  • Property schemas (types, validation rules, required fields)
  • Event definitions (types, payloads)
  • Module federation configuration
  • Custom vendor extensions (x-* fields)

Installation

pnpm add @owcs/schemas

Usage

import { getSchema, validateSchema, getAvailableVersions, AVAILABLE_SCHEMAS } from '@owcs/schemas';

// Get schema for a specific version
const schema = getSchema('1.0.0');

// Get available schema versions
const versions = getAvailableVersions();
console.log(versions); // ['1.0.0']

// Check all available schemas
console.log(AVAILABLE_SCHEMAS);

API

getSchema(version: SchemaVersion): object

Returns the JSON Schema object for the specified OWCS version. Use this to validate OWCS specifications programmatically.

Example:

const schema = getSchema('1.0.0');
// Use with AJV or other JSON Schema validators

getAvailableVersions(): SchemaVersion[]

Returns an array of all available schema versions.

Example:

const versions = getAvailableVersions();
console.log(versions); // ['1.0.0']

DEFAULT_SCHEMA_VERSION

The default schema version used when none is specified. Currently '1.0.0'.

AVAILABLE_SCHEMAS

Read-only map of all available schemas indexed by version. Useful for iterating over all schemas or checking schema availability.

Example:

import { AVAILABLE_SCHEMAS } from '@owcs/schemas';

for (const [version, schema] of Object.entries(AVAILABLE_SCHEMAS)) {
  console.log(`Schema v${version}:`, schema);
}

Schema Versions

v1.0.0 (Current)

The initial OWCS specification version includes:

  • Component definitions - Web component metadata and registration
  • Property schemas - JSON Schema-based property type definitions
  • Event definitions - Event types and payload schemas
  • Module federation - Runtime configuration for micro-frontends
  • Vendor extensions - Custom x-* fields for tooling-specific metadata

Usage in Other Packages

This package is used by:

  • @owcs/api - For validating generated specifications
  • @owcs/cli - For validation commands
  • @owcs/ui - For validating loaded YAML files

License

MIT - see LICENSE for details.