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

@basementuniverse/debug

v1.4.2

Published

A component for rendering debug output on a canvas

Readme

Game Component: Debug

A component for rendering debug output on a canvas.

Preview

Installation

npm install @basementuniverse/debug

How to use

Initialise debug before use:

import Debug from '@basementuniverse/debug';

Debug.initialise();

Render the debug output:

class Game {
  // ...

  public draw(context: CanvasRenderingContext2D) {
    // Draw everything else...

    Debug.draw(context);
  }
}

Show a value in a corner of the screen:

Debug.value('FPS', game.fps);

Show a marker somewhere on the screen:

Debug.marker('player', player.name, player.position);

Show a chart in a corner of the screen:

Debug.chart('actors', game.actors.length);

Show a border somewhere on the screen:

Debug.border('player', '', player.position, { size: player.size });

Options

const options = { ... };
Debug.initialise(options);

| Option | Type | Default | Description | | --- | --- | --- | --- | | margin | number | 10 | Edge of screen margin | | padding | number | 4 | Padding between debug text and background | | font | string | 10pt Lucida Console, monospace | The font to use | | lineHeight | number | 12 | The height of a line of text | | lineMargin | number | 0 | The margin between lines of text | | foregroundColour | string | #fff | The colour of the text | | backgroundColour | string | #333 | The colour of the background | | defaultValue | DebugValue | (see below) | Default options for values | | defaultChart | DebugChart | (see below) | Default options for charts | | defaultMarker | DebugMarker | (see below) | Default options for markers | | defaultBorder | DebugBorder | (see below) | Default options for borders |

Value options

type DebugValue = {
  label?: string;
  value?: number | string;
  align: 'left' | 'right';
  showLabel: boolean;
  padding?: number;
  font?: string;
  foregroundColour?: string;
  backgroundColour?: string;
  tags?: string[];
};

Debug.value(label, value, options);

Chart options

type DebugChart = {
  label?: string;
  values: number[];
  valueBufferSize: number;
  valueBufferStride: number;
  minValue: number;
  maxValue: number;
  barWidth: number;
  barColours?: {
    offset: number;
    colour: string;
  }[];
  align: 'left' | 'right';
  showLabel: boolean;
  padding?: number;
  font?: string;
  foregroundColour?: string;
  backgroundColour?: string;
  chartBackgroundColour?: string;
  tags?: string[];
};

Debug.chart(label, value, options);

Marker options

type DebugMarker = {
  label?: string;
  value?: number | string;
  position?: vec;
  showLabel: boolean;
  showValue: boolean;
  showMarker: boolean;
  markerSize: number;
  markerLineWidth: number;
  markerStyle: 'x' | '+' | '.';
  markerColour: string;
  markerImage?: HTMLImageElement | HTMLCanvasElement;
  space: 'world' | 'screen';
  padding?: number;
  font?: string;
  labelOffset: vec;
  foregroundColour?: string;
  backgroundColour?: string;
  tags?: string[];
};

Debug.marker(label, value, position, options);

Border options

type DebugBorder = {
  label?: string;
  value?: number | string;
  position?: vec;
  size?: vec;
  radius?: number;
  showLabel: boolean;
  showValue: boolean;
  showBorder: boolean;
  borderWidth: number;
  borderStyle: 'solid' | 'dashed' | 'dotted';
  borderShape: 'rectangle' | 'circle';
  borderColour: string;
  borderDashSize: number;
  space: 'world' | 'screen';
  padding?: number;
  font?: string;
  labelOffset: vec;
  foregroundColour?: string;
  backgroundColour?: string;
  tags?: string[];
};

Debug.border(label, value, position, options);

Tags

When rendering debug output, you can optionally specify a list of tags:

Debug.draw(context, ['tag1', 'tag2']);

Only values/markers/borders etc. which contain at least one of these tags will be rendered. This might be useful if you want to control the "level" of debug output, e.g. info/warning/error etc.

Clearing debug output (and auto-clearing)

By default, every time we render debug output (using Debug.draw(context)), the list of values/markers/borders etc. is cleared ready for the next frame. This prevents the list from growing indefinitely.

However, there might be cases where you want to call Debug.draw(context) multiple times in a single frame (especially if using tags to render different values on different canvases), in which case you might not want the list to be cleared automatically.

You can disable auto-clearing by passing false as the third arguement to Debug.draw:

Debug.draw(context, [], false);

In this case, you will need to manually clear the list of values/markers/borders etc. using Debug.clear() before the next frame.

Note that charts shouldn't usually be cleared, as they need to keep their history of values.

// Clear all values, markers, and borders
Debug.clear();

// Clear everything (including charts)
Debug.clear(true);