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

@cratis/scene.blueprint.components

v2.0.0

Published

A blueprint of Arc-bound screen and dialog templates: full pages built from Cratis Components composites, so a data list, a command form or a master-detail screen is a template rather than something you assemble.

Downloads

601

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

einarieinari

Keywords

Readme

Scene

The object model and runtime for Screenplay-based UIs: Scene.Model (platform-agnostic screens, layouts, forms, contribution points, ui profiles and themes), Scene.Engine (binding/resolution runtime), and Scene.React (the React renderer).

Packages / Deployables

Nuget NPM NPM NPM

Builds

.NET Build JavaScript Build

Description

Scene owns the object model and runtime half of the Screenplay stack. Scene.Model is the platform-agnostic C# object model that Stage translates Screenplay's parsed language constructs into, and that Studio's design-time tooling reads and writes. Scene.Engine walks that graph, resolves bindings (data, action, form, navigation contribution) and drives whichever renderer is plugged in — it does not know React exists. Scene.React is one renderer implementing the abstract vocabulary against real React/DOM; sibling positions are reserved for future Scene.Native / Scene.Desktop renderers. Vendor and internal component packages (PrimeReact, internal widget libraries) are adapters plugging into the renderer contract, not part of it.

The design-time editor built on top of this object model lives in Studio, not here — see StudioIssues#156.

Support

Cratis is an open community, and we are glad to help users, teams evaluating the stack, and contributors.

| Channel | Details | |---|---| | Discord | Join the community on Discord for questions and discussions | | GitHub Issues | Report bugs or request features | | Documentation | Read the docs at cratis.io |