partykit

#389 e3f2808 Thanks @jevakallio! - Fix deleting preview deployments

#390 2cc09ee Thanks @threepointone! - mark clipboardy as an external dependency

clipboardy comes with fallback binaries to use (esp. in windows). If we bundle it into the partykit bundle, then the references to those binaries fail. So we mark it as an external so it installs separately and resolves the binaries correctly.

#384 205d4aa Thanks @threepointone! - expose partySocket.name, and a static .url

This exposes the top level party 'name' on partysocket. Since urls for partysocket are 'static' we can also override the base implementation and expose the calculated url as well.

#386 f9a648e Thanks @threepointone! - partysocket: expose socket.room and socket.host on instance

#382 8c0bd23 Thanks @threepointone! - partysocket fix: don't crash in codesandbox

looks like tools like stackblitz defines process on the fronted (???), but when we test for process.versions.node it crashes. This fixes the detection logic.

(PartyKit doesn't work in stackblitz yet, but atleast this error shouldn't happen)

#380 22d8518 Thanks @threepointone! - add party.name

This exposes the parent level name of the party (default "main", other wise the key from parties in partykit.json

#321 5e1f03d Thanks @threepointone! - partysocket: pass custom WebSocket constructor

This lets you pass a custom WebSocket constructor to PartySocket / ReconnectingWebSocket. This means we can now run PartySocket from node.

Fixes #320

#365 5e73617 Thanks @jevakallio! - Only yield open hibernating connections to match non-hibernating behaviour + polyfill WebSocket status code on platform side

#368 a9c980f Thanks @threepointone! - update deps

#372 a9b3593 Thanks @jamesgpearce! - Reduce double ping in client.js/ts

When server hot-reloads (for example), the clients reconnect and another ping sequence starts. You then get multiple pings from each browser. This change cancels an existing sequence if it exists.

#368 a9c980f Thanks @threepointone! - update deps

#366 b79f846 Thanks @threepointone! - use npm ci for CI installs

We shouldn't use bun install until https://github.com/partykit/partykit/pull/352 lands

#366 b79f846 Thanks @threepointone! - use npm ci for CI installs

We shouldn't use bun install until https://github.com/partykit/partykit/pull/352 lands

#366 b79f846 Thanks @threepointone! - use npm ci for CI installs

We shouldn't use bun install until https://github.com/partykit/partykit/pull/352 lands

#366 b79f846 Thanks @threepointone! - use npm ci for CI installs

We shouldn't use bun install until https://github.com/partykit/partykit/pull/352 lands

#366 b79f846 Thanks @threepointone! - use npm ci for CI installs

We shouldn't use bun install until https://github.com/partykit/partykit/pull/352 lands