DocsGet started

What’s new

What changed in each version of Sluurp.

This page is Sluurp’s CHANGELOG.md, the file its version comes from. Your app can show its own the same way: see Versions and changelogs.

Unreleased

  • Built on Bun. One executable: Bun runs your server code, bundles your pages and installs your packages; Sluurp’s core is compiled in.
  • No flash of unstyled content. A component’s <link rel="stylesheet" precedence> holds the update that brings it in until its CSS has loaded, as React does.
  • React apps, with the kit. A React app is bundled for production with each screen’s code split out, compressed once and cached for good; development updates in place.
  • sluurp build. Bundles your app ahead of time and packs it, with its migrations, into one tagged file to deploy, so the server needs no packages and starts at once.
  • Plugins installed by Bun. sluurp plugin add writes them into package.json; bun.lock keeps them exact, and sluurp plugin install installs them as locked.
  • Server components and islands. Pages drawn on the server, with interactive parts that hydrate in the browser.
  • Pages and Blocks. A wiki of pages with tables, covers, history, books and an optional AI agent, for any app.
  • Search. Full-text search across relations (@@), ranked best first, with highlights; an Elasticsearch-compatible API as a plugin.
  • Queues and workflows. Background tasks claimed once and retried, and long-running workflows that sleep and wait for events.
  • Swarm mode. Several nodes, one leader taking the writes, each node with a data folder of its own.
  • Offsite backups. Every backup copied to S3-compatible storage such as Cloudflare R2, encrypted on the server with your passphrase; only what changed is sent and nothing offsite is ever deleted.
  • Twist. Pages run on Twist, one runtime under both React’s and Solid’s APIs, so an app can mix the two.
  • The client comes with Sluurp. @sluurp/client and @sluurp/react are served by the server itself, always the version it speaks; there is nothing to install.
  • Commercial plugins. Paid plugins are released sealed: encrypted, opened in the server’s memory with a key only servers that own them receive, and sold in the Marketplace. Their types and the classes they use come in the clear, so apps build on them as on any plugin.
  • A paid plugin not bought says so. An app importing a paid plugin this server hasn’t bought stops with how to get it (the Marketplace, or a business licence), not with “could not resolve”.
  • Smaller production bundles. Twist’s own code ships with short private names, and an app without spread props leaves their code out.
  • Payments as plugins. Payments left the core for a plugin, with one plugin per provider (Stripe, Mollie, Paddle, Lemon Squeezy).
  • Help in the admin. Sluurp’s documentation and each installed plugin’s are read in the admin, with live examples.
  • What server code may reach. Each function, hook and job is listed with the hosts and collections it reached; turn on Only these and anything new is refused until you allow it.
  • Account security. Each account keeps a log of its sign-ins (address, place, device), and a password change is confirmed by email with a way back. Backups → Offsite, sluurp backup --offsite, sluurp restore latest --from-offsite.

View as Markdown