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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@rbxts/rubine

v0.1.0-rc.6-ts.1

Published

An ergonomic, runtime agnostic scheduler for jecs

Downloads

96

Readme

rubine

CI Wally License: MIT

An ergonomic, runtime agnostic scheduler for Jecs

Features

Rubine provides two schedulers - one with a fairly low level interface abstracting over directly adding entities and setting components, and another abstracting over the low level one, with a "higher level" scheduler and utilities for phases.

Both can be used alongside each other, although some abstractions require to be "built" first.

In the case of pipes, they have to be either included within the abstracted scheduler

abstracted_scheduler
    :with_pipe(my_pipe, my_event)

or registered as a phase

scheduler.phase(my_pipe, my_event)

In the case of pipelines, they have to be either included within the abstracted scheduler

abstracted_scheduler
    :with_pipeline(my_pipeline, my_event)

or built

my_pipeline:build(my_event)

The abstracted scheduler starts the low level one by itself, so don't use both start functions together.

Installation

Pesde

  1. pesde add mark_marks/rubine -- In case of release candidates, do pesde add mark_marks/[email protected]_RC
  2. pesde install

Wally

  1. Add it to your wally manifest
[dependencies]
rubine = "mark-marks/rubine@LATEST" # Replace LATEST with the latest version
  1. wally install

NPM

  1. npm add @rbxts/rubine
  2. npm install

Todo

Before the 0.1.0 release, the following need to be done:

  • [ ] Unit tests
  • [x] Automatic CI & CD
  • [x] Packaging
    • [x] Pesde luau package
    • [x] Wally roblox package
  • [x] Extensibility
  • [x] Built-in Roblox scheduling extension

Mentions

Abstractions were inspired by the ecs agnostic Planck scheduler