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

@polotno/schema

v0.1.4

Published

Canonical Polotno design format: types, normalize, validate, JSON Schema. Authored in zod, DOM-free.

Downloads

1,570

Readme

@polotno/schema

TypeScript types, default values, validation, and a JSON Schema for the Polotno design JSON format — the document shape used across Polotno and its import/export packages.

Use it to validate and normalize design JSON anywhere, without running the editor.

npm install @polotno/schema

What it's for

  • Validate a design — before saving it, or when accepting it over the wire.
  • Fill in defaults so partial JSON becomes a complete, canonical document.
  • Check converter output. The import packages emit design JSON with defaults omitted; this validates and completes it. See @polotno/pdf-import, @polotno/svg-import, @polotno/psd-import.

Validate

import { validateDesign, assertValidDesign } from '@polotno/schema';

validateDesign(json, { mode: 'partial' });   // lenient — defaults may be missing
validateDesign(json, { mode: 'canonical' });  // strict — rejects unknown keys
// → { valid: boolean, errors: { path: string, message: string }[] }

assertValidDesign(json); // throws on invalid

The exported designSchemaLenient / designSchemaCanonical implement the Standard Schema interface, so they interoperate with zod, Effect Schema, Valibot, and other Standard-Schema tools.

Normalize (fill defaults)

import { normalizeDesign } from '@polotno/schema';

const complete = normalizeDesign(partial);
// every default filled in, unknown keys stripped

Idempotent and exact for current-format input. It does not migrate old schemaVersion documents, and it leaves render-derived values (e.g. text auto-height) for the editor to compute.

JSON Schema

A language-neutral JSON Schema (draft 2020-12) ships at @polotno/schema/design.schema.json — validate from any language or tooling.

import schema from '@polotno/schema/design.schema.json' with { type: 'json' };

Types

import type { Design, Page, Element, TextElement } from '@polotno/schema';

Related

License

Part of the Polotno SDK — not open source; production use requires a valid Polotno subscription. See LICENSE.md · full terms.