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

@letumfalx/phaser-plugin-debug

v1.0.0

Published

A phaser plugin that adds a debug function to your game instance.

Readme

@letumfalx/phaser-plugin-debug

A Phaser plugin that integrates the debug utility into your game instance.

Installation

# npm
npm install phaser debug @letumfalx/phaser-plugin-debug

# yarn
yarn add phaser debug @letumfalx/phaser-plugin-debug

# bun
bun add phaser debug @letumfalx/phaser-plugin-debug

Usage

Global Level

Use DebugPlugin to create a global debug.Debugger instance:

import { DebugPlugin } from "@letumfalx/phaser-plugin-debug";
import debug from "debug";
import Phaser from "phaser";

new Phaser.Game({
  plugins: {
    global: [
      {
        key: "DebugPlugin",
        plugin: DebugPlugin,
        data: {
          // Pass a namespace string to create a debug.Debugger instance
          namespace: "namespace",
          // Or pass an existing debug.Debugger instance
          namespace: debug("namespace"),
        },
        mapping: "debug",
      },
    ],
  },
  scene: [MainScene],
});

In your scene:

class MainScene extends Phaser.Scene {
  constructor() {
    super("MainScene");
  }

  create() {
    this.debug.log("this is the main scene");
    const sceneLogger = this.debug.log.extend(this.scene.key);
  }
}

To enable TypeScript support, add this declaration:

// global.d.ts
import { DebugPlugin } from "@letumfalx/phaser-plugin-debug";

declare module "phaser" {
  interface Scene {
    debug: DebugPlugin;
  }
}

Scene Level

Use SceneDebugPlugin for scene-specific instances. It automatically extends the global DebugPlugin with the namespace scene:${sceneKey}, or creates a new one if unavailable:

import { SceneDebugPlugin } from "@letumfalx/phaser-plugin-debug";
import Phaser from "phaser";

new Phaser.Game({
  plugins: {
    scene: [
      {
        key: "SceneDebugPlugin",
        plugin: SceneDebugPlugin,
        mapping: "debug",
      },
    ],
  },
  scene: [MainScene],
});

Note: When using both plugins with mapping, map them to different keys to avoid conflicts.

License

MIT