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

pixi-engine

v0.1.7

Published

Engine-like utilities for developing games with PixiJS

Downloads

6

Readme

pixi-engine

Provides a minimal engine-like structure for developing games with PixiJS.

Classes

Also, consider using other packages such as @gamestdio/mathf and @gamestdio/keycode.

Application

A singleton that extends from PIXI.Application. You might not need to use it directly. When switching scenes using SceneManager, the Application is used under the hood.

Mediator

Mediators are meant for handling business logic in your game.

import { Mediator } from "pixi-engine";

class MenuMediator extends Mediator<MenuView> {

    initialize () {
        console.log(this.view, "has been added.");
    }

    destroy () {
        console.log(this.view, "has been removed.");
    }

    onButtonClick () {
        console.log("Let's handle the click action here!");
    }

}
import { mediate, action } from "pixi-engine";

@mediate(MenuMediator)
class MenuView extends PIXI.Container {
    button: PIXI.Sprite = PIXI.Sprite.fromFrame("my-button.png");

    @action("onButtonClick")
    handleClick () {
        // handles the animation of this.button
    }

    // pixi-engine will call `update` method at every frame
    update () {
    }

    // pixi-engine will call `resize` automatically when the window is resized
    resize () {
    }
}

SceneManager

Inspired by Unity, SceneManager handles switching the current active scene. Scenes are instances of PIXI.Container.

import { SceneManager } from "pixi-engine";

class MyScene extends PIXI.Container {
    // definition of your scene
}

// Go-to target scene.
SceneManager.goTo(MyScene);

PlayerPrefs

Inspired by Unity, PlayerPrefs are meant for storing and retrieving data locally. Currently, it's just a wrapper for localStorage. In the future more adapters might be implemented to handle another storage option.

import { PlayerPrefs } from "pixi-engine";

// Key-value usage
PlayerPrefs.set("name", "Player Name");
PlayerPrefs.set("accessToken", "1f92h3f928h39f8h2");

// Object usage
PlayerPrefs.set({
    name: "Player Name",
    accessToken: "1f92h3f928h39f8h2"
});

// Retrieving data
console.log(PlayerPrefs.get("name"));

License

MIT