Stop being the product.
Become the owner.
or
sign uplog in
KernelPlay JS v0.6.0 Preview: Official TypeScript Support Is Coming!

I'm excited to announce that **KernelPlay JS v0.6.0 will officially support TypeScript!**

Starting with v0.6.0, TypeScript developers will be able to use KernelPlay JS through TypeScript declaration files (\`.d.ts\`), providing type information and better editor support.

This is another step toward making KernelPlay JS more accessible and flexible for web game developers.

**A quick development update:**

I know this update is taking longer than expected, and I apologize for the delay. Development has been slower than planned, but the new version is getting closer.

**KernelPlay JS v0.6.0 is coming very soon!**

Thank you to everyone following the project, testing it, sharing feedback, and supporting its development.

KernelPlay JS is an open-source web-based game engine, and contributions are always welcome.
#programming #js #dev #technology
show more
A server-rendered Node.js app that drives Docker: what I learned building a Minecraft server panel in plain JS

Source (MIT): https://github.com/anefzaoui/minecraft-server-manager

It's a web panel that runs Minecraft servers as Docker containers, built for the modpack servers I run for friends and family. Disclosure up front: I built it with Claude Code. I designed it, decided every feature, review the changes and test every release on our own servers, and Claude wrote most of the code. The JS choices below are the parts I think are worth talking about:

- **Plain JS, type-checked.** No build step for the server: it's JavaScript with JSDoc types, and `tsc --checkJs` runs over the core in CI. Typos in property names get caught, and stack traces point at the file you actually wrote
- **One direction of layering.** routes (parse + zod-validate, no logic) → services (the features) → docker / db / storage. A route never touches dockerode or the database directly, which made it easy to test services without Docker
- **`node:sqlite` instead of a driver.** Node 24's built-in SQLite, synchronous, WAL, with one module that owns it and a prepared-statement cache keyed on the SQL text. No native module to compile on arm64
- **dockerode, never the docker CLI.** Containers, logs, stats and image pulls all go through the Docker API, and a watcher turns Docker events into history and crash detection
- **Brokered WebSockets.** The live console opens one upstream `docker logs --follow` per server and fans it out to every open tab, instead of one stream per tab. Upgrades check `Origin` and the session cookie
- **Server-rendered.** express + Handlebars, with a small esbuild bundle for the interactive bits and CSP nonces on every response (no `unsafe-inline` scripts)
- **A path guard on every file operation.** Everything lives under one data folder, and every path is checked against escaping it, symlinks included

Tests run on `node:test` with no Docker needed, plus a live QA sweep script that hits a running panel.

Happy to go deeper on any of these, and I'd love to hear if someone has a nicer pattern for brokering log streams.
#dev #programming #js #technology
show more