GabrielSignorini

A 3D engine that draws in text.

CP437-Engine renders scenes with coloured light, shadows and traced reflections, using only text characters. There is no rendering library: projection, clipping, the z-buffer and analytic ray tracing are all written by hand, and the last pass runs on the GPU with WebGPU and a CRT effect. It began as synth-ascii-wallpaper, an outrun wallpaper drawn entirely in ASCII.

A toolkit for everyday TypeScript.

10import { clamp, toNumber, Random } from "@gabreusi/hyrax";2030clamp(5, 10, 0); // 5: bounds in either order40toNumber("abc"); // 0, never NaN5060const dm = new Random("hailtotheking");70dm.roll("1d20+5"); // attack: same every run80dm.roll("4d6kh3"); // ability score: best 3 of 490

Hyrax is a TypeScript toolkit with no runtime dependencies, and every function in it follows two rules. It takes its input in every shape that input really comes in, and types each shape exactly: the common case gets a short call, like clamp(v, max) next to clamp(v, min, max), and the return type lists every value that can come back, fallbacks included. And it has an answer for every input its types allow. Bounds work in either order, an empty range gives a neutral result where other code would give NaN, a null target does nothing, and code that needs a browser falls back quietly on the server.

Hyrax throws in one case only: a configuration no correct program can write, such as random.boolean(50) when a chance goes from 0 to 1. Bad data and a missing browser happen at run time, and the caller can't always prevent them. A bad configuration is a bug, and hiding a bug is worse than reporting it. Nothing runs at import, and a CI check breaks the build if the core ever reaches for window or document. A seed gives the same numbers in every runtime and changes them only in a major version. Every example in the docs is type-checked against the package on npm, and the ones for the core also run, so a stale answer fails the build.

Personal project · 1.0.0-rc.1 on npm · MIT