Suggest stdlib support for dgram module

[kekeqy]

As titled, suggest stdlib support for dgram module.

[proggeramlug]

UDP datagram bindings shipped as a standalone native-bindings package — same recipe as @perryts/iroh / @perryts/tursodb, no perry-stdlib changes.

• npm: @perryts/dgram
• repo: https://github.com/PerryTS/dgram
• prebuilt staticlibs (5 targets) attached to each release

Install

bun add @perryts/dgram

The package's package.json declares a perry.nativeLibrary block; Perry's compile-time resolver picks it up automatically. From your TypeScript code, import * as dgram from "dgram" works the same as any other Node module — Perry routes it to the bundled staticlib at link time.

Quick start — UDP echo server + client

Server:

import * as dgram from "dgram";

const sock = dgram.createSocket("udp4");
await dgram.bind(sock, 8000);
console.log("listening on", dgram.address(sock));

while (true) {
  const { msg, rinfo } = await dgram.recv(sock, 65_536);
  await dgram.sendBuffer(sock, msg, rinfo.port, rinfo.address);
}

Client:

import * as dgram from "dgram";

const sock = dgram.createSocket("udp4");
await dgram.bind(sock, 0); // ephemeral port
await dgram.send(sock, "hello, server!", 8000, "127.0.0.1");
const { msg } = await dgram.recv(sock, 65_536);
console.log("server replied:", new TextDecoder().decode(msg));
await dgram.close(sock);

API

createSocket / bind / send / sendBuffer / recv / close / address / setBroadcast / addMembership / dropMembership — both IPv4 + IPv6, unicast and multicast-receive.

Why await recv() instead of Node's socket.on('message', cb)

External Perry bindings can't yet register their own event-pump with perry-stdlib's event-loop dispatcher. v0.1 exposes a Promise-based recv instead, which is also the more idiomatic shape in modern TS code. Wrapping into an EventEmitter is a few lines if you need it — see the README's wrapper recipe. A native on('message', cb) API will land once perry-ffi grows per-wrapper pump registration.

Status

v0.1 covers the surface needed for unicast clients/servers + multicast group-receive workloads. Followups tracked: event-driven on(), connect(host, port) for connected-UDP semantics, setMulticastTTL / setMulticastInterface, textual interface-name resolution for IPv6 multicast.