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

@rbxts/toucan

v0.3.0

Published

<div align="center"> <img src="assets/toucan.png" width="500" /> </div>

Downloads

149

Readme

Toucan

Toucan is an opinionated Entity Component System framework for Roblox-TS that wraps over Jecs and Planck, favoring developer experience over raw performance.

It was created as a way to remove the need of glueing together different ECS libraries and allowing the developer to start working on their actual game as soon as possible.

Features

  • Fluent API: abstracts away the concept of an ECS world in favor of a more concise way of manipulating entities, queries and other things[^1];

  • Hooks: provides built-in topologically aware functions, such as useDeltaTime and useThrottledMemo;

  • Plugins: enables better organization of components and systems by grouping them together, which in turn also allows for third-party plugins that are easy to integrate;

  • Phases: inherited from Planck, systems are assigned to predefined phases[^2] in order to resolve dependencies between them;

  • Everything is an entity: inherited from Jecs, components, resources and relationships are also entities, allowing you to assign them metadata and inspect them.

[^1]: This does come with the cost of a relatively lower performance (~20-40% less than Jecs; actual benchmarks will be done and documented when things get more stable).

[^2]: Having predefined phases is what allows for third-party plugins that are easy to integrate.

Example

import { App, component, entity, pair, Plugin, query, STARTUP, Wildcard } from '@rbxts/toucan'

const Likes = component()

const bob = entity('Bob')
const charlie = entity('Charlie')
const alice = entity('Alice')
    .set(pair(Likes, bob))
    .set(pair(Likes, charlie))

function greetInterests(greeting: string) {
	query(pair(Likes, Wildcard)).forEach((subject) => {
		subject.targetsOf(Likes).forEach((interest) => {
			print(greeting.format(interest.label(), subject.label()))
		})
	})
}

class GreetingPlugin implements Plugin {
	constructor(public readonly greeting: string) {}

	build(app: App) {
		app.addSystems(STARTUP, [greetInterests], this.greeting)
	}
}

new App()
    .addPlugins(new GreetingPlugin("Hey %s, nice to meet you! I'm %s."))
    .run()

Testing Workflow

Given toucan and a test game toucan-test, in order to automatically send changes over, you must first follow the steps below a single time only:

  • On toucan, run npm run build, then yalc publish
  • On toucan-test, run yalc add @rbxts/toucan, then npm install

Then, in order to start testing toucan on toucan-test, run npm run watch on toucan.

Fallback

In case yalc fails, the script packInstall works as a fallback, packaging toucan and installing it on toucan-test. Just remember to update it to reference the right test game.