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

@modular-frontend/compositions-engine

v0.1.1

Published

Framework-neutral compositions engine: runtime, scoped stores, validation, authoring helpers, and types for arranging modules into named zones on a single screen. No UI-framework dependency — the outlet and hooks live in a binding package.

Vulnerabilities

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

Links

Git

Maintainers

kibertoadkibertoad

Keywords

Readme

@modular-frontend/compositions-engine

The framework-neutral engine behind Compositions: arrange several modules (and journeys) into named zones on a single screen, driven by a per-instance scoped store. It owns the composition runtime, scoped stores, validation, authoring helpers, and the type surface, with no UI-framework dependency.

This is the shared foundation the framework bindings build on. The React binding (@modular-react/compositions) re-exports this package and adds the UI layer (outlet, provider, hooks); a future @modular-vue/compositions will do the same over the same engine.

Installation

npm install @modular-frontend/compositions-engine

Most apps depend on a binding (@modular-react/compositions) rather than on this package directly. Use @modular-frontend/compositions-engine when building a new framework binding or framework-agnostic tooling over compositions.

What's included

  • Runtime: createCompositionRuntime, getInternals (low-level accessor the outlet drives), hydrateComposition, CompositionRuntimeOptions, and the CompositionHydrationError / UnknownCompositionError classes.
  • Validation: validateCompositionContracts, validateCompositionDefinition, and the CompositionValidationError class.
  • Scoped stores: createCompositionZoneStores, noopCompositionZoneStores, and the CompositionZoneStores type.
  • Authoring helpers: defineComposition, defineCompositionHandle.
  • Types: the full composition type surface (CompositionDefinition, CompositionInstance, CompositionRuntime, CompositionZoneMap, zone selectors, and the rest).

Full documentation

See the main documentation for the full guide.