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

@cmssy/types

v0.62.0

Published

Shared type definitions for Cmssy platform

Readme

@cmssy/types

Shared TypeScript type definitions for the Cmssy platform.

Installation

npm install @cmssy/types

Usage

import {
  FieldType,
  LayoutRegionId,
  BlockConfig,
  TemplateConfig
} from "@cmssy/types";

// Use in block.config.ts
const config: BlockConfig = {
  name: "My Block",
  category: "content",
  schema: {
    title: {
      type: FieldType.SINGLE_LINE,
      label: "Title",
    },
  },
};

Exports

  • Field Types: FieldType, FieldConfig, FieldValidation, ShowWhenCondition
  • Media values: MediaReference (assetId, transform?, altText? - empty marks the use decorative), MEDIA_ALT_TEXT_MAX, ResolvedMedia (alt is the text to render, altText the reference's own)
  • Layout: LayoutRegionId (string), LayoutRegion, DEFAULT_LAYOUT_REGIONS, LAYOUT_REGION_ID_PATTERN, LAYOUT_REGIONS_MAX, LAYOUT_REGION_LABEL_MAX
  • Modules: WorkspaceModule, FeatureFlag, BlockRequires
  • Block Config: BlockConfig, BlockSource, PackageType
  • Template Config: TemplateConfig, TemplatePageBlueprint, TemplateLayoutRegion
  • Media transform: MediaTransform, MediaTrim, MediaFit, MediaBox, FocalPoint, MEDIA_FIT_MODES, MEDIA_TRANSFORM_WIDTHS, MEDIA_TRANSFORM_MAX_SIDE, MEDIA_TRIM_MAX_SIDE, MEDIA_QUALITY_MIN, MEDIA_QUALITY_MAX, MEDIA_QUALITY_DEFAULT, parseMediaTransform, parseMediaTrim, snapWidth, snapWidthDown, renderedBox, effectiveMediaFit, transformForTrim, trimmedFocalPoint, mediaTransformUrl

Development

npm install
npm run build
npm run typecheck

Publishing

Releases are tag-driven and authenticated by OIDC trusted publishing - there is no token, and npm publish from a working copy is not the path. It would also ship whatever a previous build left in dist/, which npm run build does not clean.

npm version patch|minor|major   # bumps package.json and creates the tag
git push origin main
git push origin v<version>      # one tag, never --tags

.github/workflows/release.yml checks the tag against package.json, builds from a fresh checkout and publishes. It skips a version already on npm, so a re-run is safe - and so a tag that repeats a published version goes green having published nothing.