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

@owlmeans/wled

v0.1.11

Published

Whitelabel ("wled") core — shared types, models, and module declarations for entity-specific branding/content.

Readme

@owlmeans/wled

Whitelabel ("wled") core — shared types, models, and module declarations for entity-specific branding/content.

Overview

  • WL_PROVIDE / WL_PROVIDE_PATH — module alias and path for the whitelabel provide endpoint
  • WL_TYPE_COMPANY_INFO, WL_TYPE_STYLES, WL_TYPE_MEDIA, WL_TYPE_DNS — whitelabel content type discriminators
  • Type definitions: CompanyInfo, CustomStyles, CustomColors, CustomFont, CustomMedia, CustomBrand, ProvideParams, ProvidedWL<T>
  • modules — array containing the GET /wl/provide/:entity declaration
  • AJV models under model/ (e.g., ProvideParamsSchema)

Installation

bun add @owlmeans/wled

Usage

Use the shared module declarations and types when wiring server- and web-side whitelabel features:

import { modules as wlModules } from '@owlmeans/wled'
import type { ProvidedWL, CompanyInfo, CustomStyles } from '@owlmeans/wled'

Reference content type discriminators when filtering whitelabel records:

import { WL_TYPE_COMPANY_INFO, WL_TYPE_STYLES } from '@owlmeans/wled'

const companyInfo = await wlResource.load(`${entityId}:${WL_TYPE_COMPANY_INFO}`)

The actual server handlers live in @owlmeans/server-wl; web UI in @owlmeans/web-wl / @owlmeans/client-wl.

API

Constants

  • WL_PROVIDE'wl-provide'
  • WL_PROVIDE_PATH'/wl/provide/:entity'
  • WL_TYPE_COMPANY_INFO'company-info'
  • WL_TYPE_STYLES'styles'
  • WL_TYPE_MEDIA'media'
  • WL_TYPE_DNS'dns'

Types

CompanyInfo, CustomStyles, CustomColors, CustomFont, CustomMedia, CustomBrand, ProvideParams, ProvidedWL<T> — re-exported at the root entry.

modules

Array with one declaration: GET /wl/provide/:entity (alias WL_PROVIDE), with params filter using ProvideParamsSchema.

model

Submodule exporting AJV schemas (e.g., ProvideParamsSchema) and helpers for whitelabel records.

Related Packages

Agent guidance

This package ships embedded Claude Code skills and GitHub Copilot instructions under agent-meta/. After installing your @owlmeans/* packages, run the OwlMeans agent-skills installer to place them into your project's native locations (.claude/skills/ and .github/instructions/):

npx @owlmeans/agent-skills

The embedded files are version-matched to this package release. Do not edit them directly — they are regenerated on each publish. To contribute guidance edits, open a PR against the source monorepo.