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

pixora

v0.6.0

Published

Pixora is a declarative-by-default game framework for Pixi.js and TypeScript.

Readme

pixora

Pixora is a declarative-by-default game framework for Pixi.js and TypeScript.

Start with pixora(), describe screens with pixora.scene(), and compose menus, HUD, and overlays from layout-aware nodes and reactive state. Lower-level compatibility APIs remain available when you need imperative interop or migration paths.

Install

pnpm add pixora pixi.js

First runtime

import { pixora } from 'pixora';

const runtime = await pixora({
  backgroundColor: 0x0a0a1a,
  initialScene: 'menu',
  mount: document.querySelector('#stage'),
  scenes: [
    pixora.scene({
      key: 'menu',
      render: () => pixora.text({ text: 'Hello, Pixora!', color: '#ffffff', size: 32 }),
    }),
  ],
});

await runtime.start();

Workspace tasks

  • pnpm nx build pixora
  • pnpm nx run pixora:test --run

Gameplay scenes

For gameplay-heavy scenes, prefer a stable GameSceneShell plus a focused InPlay island.

  • keep background, HUD, and overlays in the shell;
  • keep player and dynamic entity collections in InPlay;
  • use pixora.island() for the hot gameplay surface that owns its own Pixi state;
  • use keyed host helpers such as pixora.keyedBox() for bullets, enemies, and power-ups;
  • let the scene shell stay declarative while the island patches gameplay objects directly.