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

@multisystemsuite/studio-core

v3.0.0

Published

Core schema engine, logic engine, validation, and types for MultiSystemSuite Studio

Readme

@multisystemsuite/studio-core

The foundation of MultiSystem Studio — everything else builds on this package.

What is it?

studio-core defines how apps are stored and validated:

  • JSON schema — pages, components, themes, and metadata
  • Validation — required fields, email, min/max, custom rules
  • Logic engine — show/hide fields, calculations, conditional actions
  • Types — TypeScript definitions shared across all packages

Think of it as the “brain” that understands your app structure. It does not render UI — that’s studio-renderer.

When to use it

  • Building a custom integration that reads/writes Studio JSON
  • Adding validation or logic without the visual builder
  • Registering new component types in the platform
  • Server-side schema validation

Install

pnpm add @multisystemsuite/studio-core

Quick example

import {
  createSchema,
  createComponent,
  addComponentToPage,
  exportSchema,
  importSchema,
} from '@multisystemsuite/studio-core';

// Create a blank app
const schema = createSchema({ name: 'Contact Form' });

// Add a text field to the first page
const pageId = schema.pages[0].id;
const field = createComponent('text-input', { label: 'Full Name' });
const updated = addComponentToPage(schema, pageId, field);

// Save as JSON string
const json = exportSchema(updated);

// Load back later
const loaded = importSchema(json);

Main exports

| Area | Examples | |------|----------| | Schema | createSchema, addComponentToPage, exportSchema, importSchema | | Components | createComponent, findComponent, duplicateComponent | | Validation | Rule types, validators (via validation module) | | Logic | Conditions and actions (via logic module) | | Plugins | registerPlugin, registerComponent |

Related packages

  • studio-renderer — renders schemas as React UI
  • studio-builder — visual editor that uses this schema format
  • studio-forms / studio-survey — component libraries registered on top of core types

License

MIT