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 🙏

© 2024 – Pkg Stats / Ryan Hefner

whirljs

v0.3.0-alpha.11

Published

Event-based fully documented 2D browser game engine.

Downloads

5

Readme

Features

Whirl's aim is to allow you to to quickly and easily create games in the browser; allowing you to create, extend and import game objects and plugins, making its functionality highly extendable outside of its many already included core features.

Some features offered by the Whirl game engine are:

  • Dynamic custom event system that allows for the creation and broadcasting of events across game objects.
  • Child-parent tree architecture of game objects that allows you to easily organise your game world into a managable hierarchy of objects.
  • State-like world system that makes it easy to load, unload and switch your scene or level instantly.
  • Modularised viewport manager that enables you to create multiple game viewports and screens without the need for multiple canvas elements, stacked HTML elements or duplicate game instances.
  • Flexibility-first approach that makes it easy to create your own custom plugins and game objects that can be exported and reused - objects are flexible, modular and easy to work with.

Installation and Usage

Install:

# npm
npm install whirljs

# Yarn
yarn add whirljs

Use:

// ES modules
import Whirl from "whirljs";

// UMD
window.Whirl;

Create a game:

const game = Whirl
    .createGame()
    .start();

Examples

Example usage of the various features of Whirl are included in the examples/scripts/ directory. Feel free to change and play around with them yourself!

Simply clone the repository, build the source and open up examples/Sandbox/index.html to use the in-browser code editor and get started with Whirl.

Build from Source

Whirl takes advantage of webpack to compile its source code down into a single, universally compatible JavaScript file.

  1. Clone the repository - git clone <repository url>.
  2. Install dependencies - npm i or yarn.
  3. Build from source - npm run build or yarn run build.

Once completed, you can find the built file in /build/whirl.js.

Build the Docs

Whirl uses JSDoc to write and generate its documentation.

  1. Clone the repository - git clone <repository url>.
  2. Install dependencies - npm i or yarn.
  3. Build the documentation - npm run doc or yarn run doc.

Once completed, you can find the generated documentation files in the doc/ directory, with index.html being the home page.