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

@relu-interactives/spatial-ecs

v0.5.3

Published

Reusable ECS core engine for Relu Spatial editor and runtime experiences.

Vulnerabilities

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

Links

Maintainers

calebmanteycalebmantey

Keywords

Readme

@relu-interactives/spatial-ecs

Shared ECS (Entity-Component-System) engine powering the Relu Spatial editor and preview runtimes.

What it is

@relu-interactives/spatial-ecs is the source of truth for entity/component/system behavior used across Relu Spatial experiences. It provides a deterministic, serializable scene graph that can be saved, hydrated, and executed identically in both the editor authoring environment and deployed AR/VR previews.

What it contains

| Area | Path | Description | |---|---|---| | Components | core/components/** | Runtime state containers (Transform, Model, Animation, Physics, Light, …) | | Component factories | core/factories/components/** | APIs for creating and updating component instances | | Object factories | core/factories/objects/** | Entity assembly — wires baseline components onto scene objects | | Systems | core/systems/** | Frame-by-frame runtime behavior and scene synchronization | | World | core/World.ts | ECS storage, lifecycle, system scheduling, snapshot and history management | | Hydration | core/hydration/** | World reconstruction from saved snapshot data | | Snapshot utils | core/worldSnapshotUtils.ts | Snapshot normalization, cloning, and debug helpers | | Scripting | core/Behaviour.ts, core/ScriptTemplate.ts | Base classes for user-authored ECS scripts |

Installation

npm install @relu-interactives/spatial-ecs
# or
pnpm add @relu-interactives/spatial-ecs

three is a peer dependency and must be installed separately:

npm install three

Local Development

pnpm install
pnpm run build
pnpm run typecheck

Key Concepts

Entities and Components

Entities are integer IDs. Components are plain data containers attached to entities and stored in the World. Systems query for entities that have specific component combinations and apply runtime behavior each frame.

Snapshot and Hydration

The world can be serialized to a plain JSON snapshot and fully reconstructed via hydrateWorldFromSnapshotDetailed. Snapshots are designed to be forward-compatible — hydration is tolerant of missing or legacy fields.

Editor / Preview Parity

The same component contracts, factory logic, and hydration path are used by both the editor and the preview runtime. Changes to any of these must preserve behavior across both consumers.