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

@optimizely/cms-sdk

v2.2.0

Published

JavaScript tools for integration with Optimizely CMS

Readme

@optimizely/cms-sdk

npm version

The official JavaScript/TypeScript SDK for building headless applications with Optimizely CMS. This library provides everything you need to fetch, render, and manage content from Optimizely CMS with full type safety and intelligent code completion.

Features

  • Type-safe content modeling - Full TypeScript definitions for your content types
  • Framework integration - First-class support for React and Next.js
  • Live preview - Real-time content editing experience
  • Rich text rendering - Advanced rich text component with extensibility
  • DAM integration - Seamless digital asset management

Installation

npm install @optimizely/cms-sdk

Or using other package managers:

# pnpm
pnpm add @optimizely/cms-sdk

# yarn
yarn add @optimizely/cms-sdk

Quick Start

// Initialize the client
const client = new GraphClient('<YOUR_APP_SINGLE_KEY>', {
  graphUrl: 'https://your-cms-instance.com',
});

// Fetch content
const c = await client.getContentByPath(`/<SOME_URL>`);

Documentation

Full guides and documentation in the main repository:

Getting Started

  • Installation - Set up your development environment
  • Setup - Configure the SDK and CLI
  • Modelling - Define your content types with TypeScript

Core Features

Schema Validation

Validate content data (e.g. GraphQL responses) against your content type definitions at runtime using toSchema().

import { toSchema, SchemaValidationError } from '@optimizely/cms-sdk/schema';
import { BlogPageCT } from './content-types/BlogPageCT';

const schema = toSchema(BlogPageCT);

safeParse() — validate without throwing

Returns { success: true, data } or { success: false, errors }. Use when you want to handle errors yourself.

const result = schema.safeParse(graphqlResponse);

if (result.success) {
  // result.data is fully typed based on the content type definition
  console.log(result.data.title);
  console.log(result.data.p_heroImage);
} else {
  // result.errors is an array of ValidationError
  result.errors.forEach(err => {
    console.error(`[${err.path.join('.')}] ${err.message}`);
  });
}

parse() — validate or throw

Returns the validated data, or throws SchemaValidationError on failure. Use when invalid data should stop execution.

try {
  const page = schema.parse(graphqlResponse);
  console.log(page.title);
} catch (err) {
  if (err instanceof SchemaValidationError) {
    console.error(`${err.errors.length} validation error(s)`);
    err.errors.forEach(e => console.error(e.message));
  }
}

Strict mode

By default, extra properties not defined in the content type are allowed (passthrough). Use { strict: true } to reject them.

const strictSchema = toSchema(BlogPageCT, { strict: true });

const result = strictSchema.safeParse({
  ...validData,
  unknownField: 'value', // will cause validation to fail
});

What gets validated

| Check | Example | |---|---| | Required base fields | _id, __typename, _metadata must be present at root | | Type correctness | p_integer must be number, not string | | Constraints | minimum/maximum, minLength/maxLength, pattern | | Enum values | Value must be one of the allowed enum values | | Array bounds | minItems/maxItems | | Nested structures | richText, contentReference, component, array validated recursively |

Top-level content properties (p_string, p_xhtml, etc.) are optional — null or undefined values are skipped. Sub-fields within complex types (e.g. html/json in richText, key in contentReference) are also optional and only validated when present and non-null.

Advanced Features

Best Practices

This SDK works best when used with the @optimizely/cms-cli package, which enables code-first content modeling by syncing your TypeScript definitions to Optimizely CMS.

npm install -D @optimizely/cms-cli

For complete setup instructions, see the main repository README.

Support

License

Apache License 2.0


Built by the Optimizely CMS Team | Documentation | GitHub