Stack picker
What would a dev do?
A few questions about what you're building, then the playbook a developer would reach for — and when to skip it.
A dev would reach for
3D web game: Three.js + Rapier + Vite
3D games and explorable worlds that run in a browser tab — a link instead of an install.
Why this fits
- A browser game should load instantly from a link.
- Three.js is the most widely used 3D library for the web, and Rapier adds real physics compiled to WebAssembly.
- You keep control of the architecture instead of adopting an engine's editor.
Common trap
Ignoring download size and draw calls until late — mobile browsers run out of memory long before desktops do.
Check this before you commit
Skip if the game needs large worlds, console releases, or an editor-driven workflow for designers — a full engine such as Godot or PlayCanvas fits better.
Read the playbookAlso consider
Babylon.js + TypeScript + ViteIf a code-first engine API with scene and asset systems fits the team.PlayCanvas + entities and scriptsIf entity/component composition and optional hosted visual authoring fit the project.Godot + GDScriptIf a desktop or store release ends up mattering as much as the link.Phaser + TypeScript + ViteIf the game can be 2D — Phaser covers far more out of the box.