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/jecs-topo-runtime

v0.0.3

Published

A Runtime for Jecs

Downloads

13

Readme

jecs-topo-runtime

This package does not really depend on the jecs functionality. This package will probably eventually be branched out into an abstract topo runtime package.

Basic Setup

const world = new World()
const loop = new Loop(world, ...some other arguments that will be passed to systems)

const connection = loop.begin(RunService.Heartbeat)

const system = (arguments from loop constructor call) => {
    // some work
}

loop.scheduleSystem(system)

// hot reload stuff
loop.evictSystem(system)
// or more convenient
loop.replaceSystem(system, () => {})

Builtin hooks

useEvent useThrottle

There is useHookState function for implementing custom hooks.

Side note

Not a single test has been written for the package so it may contain There has not been written any test