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

@manifest-editor/creator-api

v2.1.0

Published

- What do you want to create - The type + refined type - The fields you add - Static fields - Where is it valid to create - Parent type - Custom parent supports - Parent fields - Canvas specific: how does it affect the canvas - temporal -

Downloads

1,259

Readme

Creator API

  • What do you want to create
    • The type + refined type
    • The fields you add
    • Static fields
  • Where is it valid to create
    • Parent type
    • Custom parent supports
    • Parent fields
  • Canvas specific: how does it affect the canvas
    • temporal
    • spatial
  • What can it export as:
    • Canvas
    • Annotation
    • Resource
  • Other
    • Does it replace resources? (e.g. choice)
    • Does it require canvas interaction

Examples (cookbook)

  • Simple image
  • Simple audio
  • Simple video
  • Image with service
  • Cropped image (with service)
  • External HTML link
  • External PDF
  • External XML
  • External plaintext?
  • Commenting annotation on canvas
  • Tagging annotation at box
  • Creating range from canvas selection?
  • Creating choice from list of annotations

The creation process is split into two parts:

  • The UI (e.g. the form that's presented to the user)
  • The building/creation process

The creation process is intended to be dual purpose. This is not a great example, but here you can see that you can "call" other creators inside this creator. So they can become composable.

async function createThing(ctx) {
  const image = await ctx.create("@manifest-editor/create-image", {
    url: "https://example.org/image-1.jpg",
  });

  // If you want the underlying resource you just created.
  const previewResource = image.get();

  // Find a reference to an existing resource.
  const ref = ctx.ref("https://example.org/canvas-1");

  // Or you can create new resources that will be embedded.
  const image2 = ctx.embed({
    id: "https://example.org/image-2.jpg",
    type: "Image",
    height: 100,
    width: 200,
  });

  // And then it can be part of a bigger resource:
  // This cannot be a nested tree - it must be a flat resource with linked resources (like thumbnail) as
  // objects like `ctx.create()` or `ctx.embed()`. This makes sure that we can piece together the finaly
  // actions required in the last step.
  return {
    id: "https://example.org/image-3.jpg",
    type: "Image",
    height: ctx.data.height,
    width: ctx.data.width,
    thumbnail: [image],
  };
}

A "create" callback will be passed to the render, this is when this will be called and the resource will be created. Once created edit() will be called on the resource.