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

@portabletext/schema

v2.2.2

Published

Portable Text Schema

Readme

@portabletext/schema

A TypeScript library for defining and compiling Portable Text schemas with full type safety and editor support.

Installation

npm install @portabletext/schema

Usage

Define a schema

import {defineSchema} from '@portabletext/schema'

const schemaDefinition = defineSchema({
  styles: [{name: 'normal'}, {name: 'h1'}, {name: 'h2'}, {name: 'blockquote'}],
  decorators: [{name: 'strong'}, {name: 'em'}],
  annotations: [{name: 'link'}],
  lists: [{name: 'bullet'}, {name: 'numbered'}],
})

Compile schema

import {compileSchema} from '@portabletext/schema'

const schema = compileSchema(schemaDefinition)

Containers and sub-schemas

A block object can act as a container: one of its fields is an array whose of includes a {type: 'block'} member, which declares the text sub-schema allowed inside it. This is how a code block, callout, or table cell restricts what can be typed within it.

const schemaDefinition = defineSchema({
  decorators: [{name: 'strong'}, {name: 'em'}, {name: 'code'}],
  styles: [{name: 'normal'}, {name: 'h1'}],
  blockObjects: [
    {
      name: 'code-block',
      fields: [
        {
          name: 'lines',
          type: 'array',
          of: [
            // A code line: a `code` style only, and no decorators.
            {type: 'block', styles: [{name: 'code'}], decorators: []},
          ],
        },
      ],
    },
  ],
})

Use getSubSchema to resolve what is allowed at a position inside a container. It returns a Schema you can treat like any top-level one:

import {compileSchema, getSubSchema} from '@portabletext/schema'

const schema = compileSchema(schemaDefinition)
const codeBlock = schema.blockObjects.find((type) => type.name === 'code-block')
const lines = codeBlock.fields.find((field) => field.name === 'lines')

const subSchema = getSubSchema(schema, lines.of)
// subSchema.decorators === []                 (the code line forbids decorators)
// subSchema.styles     === [{name: 'code', ...}] (only the `code` style)

How a nested block overrides and inherits

Each of styles, decorators, annotations, lists, and inlineObjects resolves independently:

  • Declared overrides for that property.
  • Declared empty ([]) overrides to nothing, e.g. decorators: [] forbids every decorator inside the container.
  • Absent inherits from the nearest enclosing container that declares a block, or the root when none does.

There is no merging: a property is either declared here or taken whole from a single source. An absent property resolves against the nearest enclosing container whose block declares it, so a block nested inside a container that restricts its own text inherits that restriction rather than the document root. It falls back to the root only when no enclosing container declares a block of its own (e.g. structural tablerowcell wrappers, where the cell's text inherits the document). A nested block never blends multiple ancestors; it takes exactly one inherited value. When the of has no {type: 'block'} member at all, the container allows objects only, with no text formatting.