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

@dynostack/react-studio

v0.1.0

Published

Controlled React builders for forms, schedules, dashboards, workflows, project plans, documents and charts.

Downloads

272

Readme

Dynostack React Studio

Eight controlled React modules for business workflows. Published independently as @dynostack/react-studio; it does not depend on React Grid.

| Import | Component | Model | | ----------------------------------- | ------------------ | ---------------- | | @dynostack/react-studio/forms | FormBuilder | FormSchema | | @dynostack/react-studio/scheduler | Scheduler | Schedule | | @dynostack/react-studio/dashboard | DashboardBuilder | Dashboard | | @dynostack/react-studio/workflow | WorkflowDesigner | Workflow | | @dynostack/react-studio/gantt | GanttPlanner | ProjectPlan | | @dynostack/react-studio/document | DocumentEditor | StudioDocument | | @dynostack/react-studio/application | ApplicationDesigner | ApplicationDiagram | | @dynostack/react-studio/charts | ChartExplorer | ChartConfig |

Install

npm install @dynostack/react-studio

Build locally

From this directory, run npm install, npm run typecheck, npm run build, npm test, and npm pack. Install the generated .tgz in your React application. In this repository, build tools and React can resolve from the parent node_modules without another install.

Import @dynostack/react-studio/styles.css once. CSS is scoped to .ds-tool and does not require Tailwind, Radix, the data grid, or a runtime chart library. Individual subpath imports keep unrelated modules out of your application's entry point. React 18.2+ is a peer dependency.

import { useState } from 'react'
import { FormBuilder } from '@dynostack/react-studio/forms'
import type { FormSchema } from '@dynostack/react-studio'
import '@dynostack/react-studio/styles.css'

const initial: FormSchema = {
  version: 1,
  title: 'Contact',
  description: 'Tell us about your project.',
  steps: ['Details'],
  fields: [
    {
      id: 'email',
      label: 'Work email',
      type: 'email',
      step: 0,
      required: true,
    },
  ],
}
export function Intake() {
  const [value, setValue] = useState(initial)
  return (
    <FormBuilder
      value={value}
      onChange={setValue}
      onSubmit={async (response) => {
        const result = await fetch('/api/intake', {
          method: 'POST',
          headers: { 'Content-Type': 'application/json' },
          body: JSON.stringify(response),
        })
        if (!result.ok) throw new Error('Could not submit. Please try again.')
      }}
    />
  )
}

State and persistence

Every component takes value and onChange(nextValue). The application owns the model; changes are immutable. IDs must be stable and unique. Exported configurations have version: 1 and contain serializable data. They do not contain callbacks, upload contents, or credentials.

FormBuilder.onSubmit(values) receives visible field values after validation. Scheduler.onSaveEvent(event) is awaited before the event is committed to the controlled schedule. DashboardBuilder, WorkflowDesigner, GanttPlanner, and DocumentEditor expose onSave(model). Return a promise to show saving state; throw an Error to display a failure and keep edits for retry. Schedule deletion is an onChange operation; applications must persist the updated collection themselves. ChartExplorer.onDrillDown(point) reports a selected period.

The showcase at /studio?tool=forms includes working sample configurations, JSON download/copy, integration examples and save-failure simulation. Its save adapter stores selected data in browser local storage; it is not a production backend, and editable sessions are not automatically restored after refresh. Backend callbacks must enforce authentication, authorization, validation and concurrency rules on the server.

Public helpers

The ./core entry exports types and pure helpers: validateFormSchema, validateForm, formSubmission, fieldVisible, expandEvents, validateEvent, validateWorkflow, simulateWorkflow, validatePlan, reschedulePlan, criticalPath, validateChart, chartCsv, shiftDate, dateDistance, moveItem and csvCell.

Scheduler events store ISO instants; task dates store YYYY-MM-DD calendar dates. Weekly recurrence is bounded to one year by the appointment editor and repeats in UTC. Finish-to-start tasks begin on a calendar day after dependencies finish.

Styling and accessibility

Override --ds-bg, --ds-surface, --ds-soft, --ds-text, --ds-muted, --ds-border, --ds-accent, --ds-accent-soft and --ds-edge on .ds-tool to customize colors. All controls have native keyboard access. Forms and widgets have reorder buttons; workflow nodes move with arrows; Gantt bars move with left/right arrows. Charts expose data point buttons instead of requiring pointer hover. Motion is not required and reduced-motion preferences are respected.

See FEATURES.md for the implemented scope and remaining advanced capabilities.

Application architecture and component blocks

ApplicationDesigner is exported from @dynostack/react-studio/application. It accepts value: ApplicationDiagram, onChange and optional async onSave. The diagram model contains component nodes, typed connectors and architecture notes. Use canvas, code or split mode. The code pane accepts the version 1 JSON schema; Apply rejects invalid IDs, unsupported kinds, coordinates outside +/-10000 and more than 100 nodes / 300 connectors. Cycles are supported for architecture.

Select and drag a node or focus the canvas and move the selected node with arrow keys (Shift moves 25 units). Connect two components with the Connect tool or node ports. Select a connector to edit its label, protocol and curve/elbow/straight style. Pan, zoom, fit, erase, undo/redo, SVG, JSON and Markdown exports are local. The walkthrough describes each node and connector. Connector types document contracts; they do not provision services or connect accounts.

Charts default to shape-preserving cubic interpolation. Set curve to monotone, linear or step, markers to show all points and animated: false to disable entry motion. Hover inspection, keyboard period buttons, range sliders and a drag range selection are available. ChartView also supports sparkline and onRangeSelect. MetricCard combines a KPI and a sparkline. Reduced-motion preferences disable animation.

The showcase /blocks gallery has ten live blocks, filters, search, preview/code, 375px preview widths, replay and copyable integration examples. Studio and Blocks consume the site's existing graphite theme tokens in both appearance modes. Standalone CSS defaults to neutral light; override --ds-* on a .ds-tool container for your application theme.