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

@evitcastudio/kit

v3.0.1

Published

A single-player/multiplayer framework for the Vylocity Game Engine.

Readme

Kit

Kit is a lightweight, extensible 2D framework for game development in the Vylocity Game Engine. Designed to be simple and modular, Kit empowers developers to build complex projects quickly through a robust plugin-driven architecture.

Installation

bun install -g @evitcastudio/kit

Note: The -g flag ensures the kit CLI tool is globally available in your PATH.

Scaffolding a New Project

The kit init command provides an interactive walkthrough to quickly scaffold a new project for the Vylocity Game Engine.

# Start the interactive walkthrough
kit init

# Or scaffold a project with flags
kit init <project-name> --single # For single-player
kit init <project-name> --multi  # For multiplayer

The command will create a structured directory for your project, including pre-configured package.json, essential Vylocity files, and a local development environment.

After scaffolding, follow these steps to get started:

  1. cd <project-name>
  2. bun install
  3. bun run build

Building the Project

Note: This process is preconfigured for you if you used kit init

The kit build command locates all Vylocity engine-related resources in your source directory, anonymizes them, and moves them to a deploy-ready output directory.

kit build -i ./<in-dir> -o ./<out-dir>
# To learn more about this command
kit build --help

Executing this command automatically generates a resource.json map in your project's directory. Best Practice: Exclude resource.json from version control (.gitignore), as it is a build artifact.

Runtime Resource Loading

Note: This process is preconfigured for you if you used kit init

Kit.setResources() should be called before VYLO.load().

import resourceJSON from 'resource.json';

// Initialize the engine with mapped resources
await Kit.setResources(resourceJSON);

Local Development & Testing

Once your project is scaffolded and dependencies are installed and the project has been built, you can run your game locally.

Running the Game

# For Single-Player or Multiplayer games
bun run host

Accessing the Game

The server will be available at the following locations after being hosted:

Singleplayer
http://localhost:8090 defined in ./bun-serve.ts

Multiplayer or Singleplayer & Multiplayer
http://localhost:30000 defined in ./src/server/settings.json

Plugin Architecture

import { Plugin } from 'custom-plugin';

// Register a single plugin
const plugin = Kit.registerPlugin(Plugin);
// Register multiple plugins
import { Plugin1 } from 'custom-plugin1';
import { Plugin2 } from 'custom-plugin2';

const plugins = Kit.registerPlugins([Plugin1, Plugin2]);

// After being registered, kit can find the plugin by name.
const plugin1 = Kit.getPlugin('plugin1-name');
const plugin2 = Kit.getPlugin('plugin2-name');

Listening for plugin events

Plugins emit events, this is how they pass relevant data to other plugins or the main thread. By listening to these events you can act on this data.

const listener = (pEvent: EmitterEvent) => {
    const { data, timestamp } = pEvent;
    // Here you can use the data that the event sent down.
}

// Choose to listen to specific event from a plugin
Kit.on('plugin-name', 'event-name', listener);

// You can also stop listening for an event
Kit.off('plugin-name', 'event-name', listener);

For more information check out the wiki