<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Jamie Barton</title>
    <description>The latest articles on DEV Community by Jamie Barton (@notrab).</description>
    <link>https://dev.to/notrab</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3168%2F5981a8ab-d2de-4cd9-971f-fb1fec8cb5b2.jpg</url>
      <title>DEV Community: Jamie Barton</title>
      <link>https://dev.to/notrab</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/notrab"/>
    <language>en</language>
    <item>
      <title>Build and deploy scripts at the edge with the bunny.net CLI</title>
      <dc:creator>Jamie Barton</dc:creator>
      <pubDate>Thu, 12 Nov 2026 11:54:11 +0000</pubDate>
      <link>https://dev.to/bunnydotnet/build-and-deploy-scripts-at-the-edge-with-the-bunnynet-cli-5ajn</link>
      <guid>https://dev.to/bunnydotnet/build-and-deploy-scripts-at-the-edge-with-the-bunnynet-cli-5ajn</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published at bunny.net on June 10, 2026. Since then, the bunny.net CLI has expanded beyond Bunny Database and Edge Scripting. Find out more &lt;a href="https://bunny.net/docs/cli" rel="noopener noreferrer"&gt;in the docs&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;A few weeks ago we &lt;a href="https://bunny.net/blog/introducing-the-bunny-net-cli/" rel="noopener noreferrer"&gt;introduced the bunny.net CLI&lt;/a&gt;, one command-line tool for managing your entire bunny.net stack. That first release shipped with full Database support, and we promised more would follow.&lt;/p&gt;

&lt;p&gt;Today, &lt;strong&gt;&lt;a href="https://docs.bunny.net/scripting" rel="noopener noreferrer"&gt;Edge Scripting&lt;/a&gt;&lt;/strong&gt; lands in the CLI.&lt;/p&gt;

&lt;p&gt;You can scaffold a new script from a template, develop and test it locally with Node or Deno, deploy a built bundle to the global network, manage environment variables, and step through deployment history from your terminal.&lt;/p&gt;

&lt;h2&gt;
  
  
  A two-minute tour
&lt;/h2&gt;

&lt;p&gt;If you've already got the CLI installed and you're logged in, three commands will get you to a deployed function:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;bunny scripts init --name my-edge-app --type standalone --template &lt;span class="s2"&gt;"Return JSON"&lt;/span&gt; --deploy
&lt;span class="nb"&gt;cd&lt;/span&gt; my-edge-app
npm run build
bunny scripts deploy dist/index.js
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;If you haven't installed the CLI yet, do that first:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npm install -g @bunny.net/cli
bunny login
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Scaffold a project from a template
&lt;/h2&gt;

&lt;p&gt;&lt;code&gt;bunny scripts init&lt;/code&gt; creates a new edge script project on your machine. Run it with no flags and the CLI walks you through it interactively, asking you to pick a template, name the project, and choose whether to install dependencies:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;bunny scripts init
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;You can also pass everything as flags, which is handy when you're in a hurry or when an agent is driving:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;bunny scripts init \
  --name my-edge-app \
  --type standalone \
  --template &lt;span class="s2"&gt;"Return JSON"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Add &lt;code&gt;--deploy&lt;/code&gt; to also create the remote script on bunny.net and link the directory in the same step. Without it, &lt;code&gt;init&lt;/code&gt; only scaffolds the local project, and you create the remote script later with &lt;code&gt;bunny scripts create&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;The built-in templates are &lt;code&gt;Empty&lt;/code&gt;, &lt;code&gt;Return JSON&lt;/code&gt;, and &lt;code&gt;Simple Middleware&lt;/code&gt;. Each one comes with a working project layout and sensible defaults so you can build and deploy straight away.&lt;/p&gt;

&lt;p&gt;You can also bring your own template from a Git repo:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;bunny scripts init --name my-edge-app --repo user/my-template
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Custom templates always prompt before installing dependencies, since a template's install scripts run on your machine. Review the repo before you let it install.&lt;/p&gt;

&lt;h2&gt;
  
  
  Run it locally
&lt;/h2&gt;

&lt;p&gt;Edge Scripts are JavaScript and TypeScript projects built on Web-standard APIs. You develop them locally with your own editor and the debugging tools you already use.&lt;/p&gt;

&lt;p&gt;The CLI auto-detects your package manager from the template's lockfile (bun, npm, pnpm, or yarn) and uses the template's own dev and build scripts:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;cd&lt;/span&gt; my-edge-app
npm install
npm run dev
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The CLI doesn't yet ship a custom runtime emulator. It wraps the tools you'd reach for anyway, so local development stays fast and predictable.&lt;/p&gt;

&lt;h2&gt;
  
  
  Link a directory to a script
&lt;/h2&gt;

&lt;p&gt;Once you've got something you want to deploy, connect the working directory to a script on bunny.net:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;bunny scripts link
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Run it once, and it writes a small &lt;code&gt;.bunny/script.json&lt;/code&gt; manifest into your project that records which script on bunny.net this directory belongs to. From that point on, every other &lt;code&gt;scripts&lt;/code&gt; command knows what you're targeting:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;bunny scripts deploy&lt;/code&gt; deploys this project&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;bunny scripts env set API_KEY=...&lt;/code&gt; writes to this script's environment&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;bunny scripts deployments list&lt;/code&gt; shows this script's history&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The script ID stays out of your shell history, and you don't pass it on every command. Run &lt;code&gt;bunny scripts link&lt;/code&gt; with no flags to choose from a list, or &lt;code&gt;bunny scripts link --id 12345&lt;/code&gt; to link directly.&lt;/p&gt;

&lt;p&gt;The manifest holds per-developer state, so it shouldn't be committed. &lt;code&gt;bunny scripts init&lt;/code&gt; adds &lt;code&gt;.bunny/&lt;/code&gt; to your &lt;code&gt;.gitignore&lt;/code&gt; automatically. If you ran &lt;code&gt;bunny scripts link&lt;/code&gt; or &lt;code&gt;bunny scripts create&lt;/code&gt; in an existing repo, add &lt;code&gt;.bunny/&lt;/code&gt; to &lt;code&gt;.gitignore&lt;/code&gt; yourself, then anyone who clones the repo links their own script.&lt;/p&gt;

&lt;p&gt;For those deploying scripts in CI, you can skip the project linking by passing the Edge Script ID when you deploy:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;bunny scripts deploy dist/index.js 12345
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Build and deploy
&lt;/h2&gt;

&lt;p&gt;Edge Scripts deploy as a single built bundle. The CLI doesn't build for you, so run the template's own build step first, then point deploy at the output:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npm run build
bunny scripts deploy dist/index.js
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;code&gt;deploy&lt;/code&gt; uploads the file as a new release and publishes it live by default. On success it prints the script's live hostname:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;✓ Published my-edge-app
  https://my-edge-app.bunny.run
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;If you want to upload a release without publishing it, stage it with &lt;code&gt;--skip-publish&lt;/code&gt; and publish later.&lt;/p&gt;

&lt;h2&gt;
  
  
  Put it on your own domain
&lt;/h2&gt;

&lt;p&gt;Every script gets a &lt;code&gt;bunny.run&lt;/code&gt; URL, but you can also bring your own domain. We've made it super easy with a new command:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;bunny scripts domains add shop.example.com
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;code&gt;bunny scripts domains add&lt;/code&gt; sets up HTTPS on your own domain. bunny.net issues SSL certificates for free and can do so as soon as your DNS points to the network, so the command prints the exact CNAME record to create, along with the follow-up command to run. Once DNS has propagated, request your certificate:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;bunny scripts domains ssl shop.example.com
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;HTTPS is enforced by default, so anyone arriving over &lt;code&gt;http://&lt;/code&gt; is redirected.&lt;/p&gt;

&lt;p&gt;List a script's domains any time to check their SSL status:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;bunny scripts domains list
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Manage environment variables and secrets
&lt;/h2&gt;

&lt;p&gt;Most edge functions need configuration values like API tokens, feature flags, or region hints. The CLI handles two kinds. Plain &lt;strong&gt;variables&lt;/strong&gt; are stored on bunny.net and can be read back. &lt;strong&gt;Secrets&lt;/strong&gt; are encrypted, and their values can never be read back once set:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;bunny scripts env &lt;span class="nb"&gt;set&lt;/span&gt; DATABASE_URL &lt;span class="s2"&gt;"libsql://..."&lt;/span&gt;
bunny scripts env &lt;span class="nb"&gt;set&lt;/span&gt; API_KEY &lt;span class="s2"&gt;"sk_..."&lt;/span&gt; --secret
bunny scripts env list
bunny scripts env remove API_KEY
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Names are uppercased automatically, and a name can be a variable or a secret but not both. &lt;code&gt;env list&lt;/code&gt; shows secret values as blank, since the API never returns them.&lt;/p&gt;

&lt;p&gt;To pull plain variables into a local file for development, use &lt;code&gt;env pull&lt;/code&gt;. It writes &lt;code&gt;NAME=VALUE&lt;/code&gt; lines to &lt;code&gt;.bunny/.env&lt;/code&gt;. Secrets are never included, so keep their source values somewhere safe:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;bunny scripts env pull
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Listing supports &lt;code&gt;--output json&lt;/code&gt;, useful for diffing or syncing with another tool:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;bunny scripts env list --output json &lt;span class="o"&gt;|&lt;/span&gt; jq &lt;span class="s1"&gt;'.[].name'&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Deployment history
&lt;/h2&gt;

&lt;p&gt;Every release is recorded, and the CLI gives you a view into that history:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;bunny scripts deployments list
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;





&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;ID       Status      Author   Released   Published
14021    ● Live      jamie    2m ago     yes
14008    ○ Archived  jamie    1h ago     yes
13990    ○ Archived  jamie    1d ago     yes
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The live release is marked with a filled dot, and archived releases are marked with an open one. If a release is live and the script has a linked pull zone, the hostname is printed at the end.&lt;/p&gt;

&lt;p&gt;Need to roll back? You don't have to rebuild anything. The bundle for every past release is already on bunny.net, so grab the ID of a known-good one from that list and republish it:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;bunny scripts deployments publish 13990
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This flips which release is live without re-uploading anything, so a bad deploy can be undone in seconds. &lt;code&gt;deploy&lt;/code&gt; ships new code. &lt;code&gt;publish&lt;/code&gt; re-promotes a release that has already shipped.&lt;/p&gt;

&lt;h2&gt;
  
  
  See how it's doing
&lt;/h2&gt;

&lt;p&gt;Once a script is serving traffic, you'll want to know how much traffic it's handling and what it's costing. &lt;code&gt;bunny scripts stats&lt;/code&gt; pulls request, CPU, and cost totals for the script and draws a per-day bar chart of requests served right in your terminal:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;bunny scripts stats

Key                   Value
Script                bunny-cards
Period                last 30 days
Total Requests        1,455
Total CPU             43,336ms
Avg CPU / Execution   29.78ms
Total Cost            $0.00

Requests served
May 18, 2026  ░░░░░░░░░░░░░░░░░░░░░░░░    0
May 19, 2026  ████████████████████████  504
May 20, 2026  ██████████████████░░░░░░  383
May 21, 2026  ░░░░░░░░░░░░░░░░░░░░░░░░    0
May 22, 2026  ░░░░░░░░░░░░░░░░░░░░░░░░    0
May 23, 2026  ░░░░░░░░░░░░░░░░░░░░░░░░    0
May 24, 2026  ░░░░░░░░░░░░░░░░░░░░░░░░    0
May 25, 2026  █░░░░░░░░░░░░░░░░░░░░░░░    4
May 26, 2026  ░░░░░░░░░░░░░░░░░░░░░░░░    0
May 27, 2026  █░░░░░░░░░░░░░░░░░░░░░░░    5
May 28, 2026  ██░░░░░░░░░░░░░░░░░░░░░░   37
May 29, 2026  ████░░░░░░░░░░░░░░░░░░░░   90
May 30, 2026  ░░░░░░░░░░░░░░░░░░░░░░░░    0
May 31, 2026  ░░░░░░░░░░░░░░░░░░░░░░░░    0
Jun 1, 2026   ░░░░░░░░░░░░░░░░░░░░░░░░    0
Jun 2, 2026   ░░░░░░░░░░░░░░░░░░░░░░░░    0
Jun 3, 2026   ░░░░░░░░░░░░░░░░░░░░░░░░    0
Jun 4, 2026   ███████████░░░░░░░░░░░░░  223
Jun 5, 2026   █████████░░░░░░░░░░░░░░░  191
Jun 6, 2026   █░░░░░░░░░░░░░░░░░░░░░░░   11
Jun 7, 2026   █░░░░░░░░░░░░░░░░░░░░░░░    5
Jun 8, 2026   █░░░░░░░░░░░░░░░░░░░░░░░    2
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;By default, it covers the last 30 days. Narrow the window with &lt;code&gt;--from&lt;/code&gt; and &lt;code&gt;--to&lt;/code&gt;, or switch to an hourly breakdown when you're chasing a spike:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;bunny scripts stats --from 2026-05-01 --to 2026-05-31
bunny scripts stats --hourly
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Like everything else, it uses your linked script when you don't pass an ID, and &lt;code&gt;--output json&lt;/code&gt; gives you the data to pipe into whatever you use to track usage.&lt;/p&gt;

&lt;h2&gt;
  
  
  Works with your agent and CI
&lt;/h2&gt;

&lt;p&gt;Prompts and spinners are TTY-aware, so they disappear in CI. Commands support &lt;code&gt;--output json&lt;/code&gt;, and destructive commands like &lt;code&gt;delete&lt;/code&gt; and &lt;code&gt;env remove&lt;/code&gt; take &lt;code&gt;--force&lt;/code&gt; so they don't block on a confirmation prompt in a pipeline.&lt;/p&gt;

&lt;p&gt;In CI you can skip the global install and run the CLI through &lt;code&gt;npx&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight yaml"&gt;&lt;code&gt;&lt;span class="c1"&gt;# .github/workflows/deploy.yml
&lt;/span&gt;&lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="na"&gt;run&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;npm ci&lt;/span&gt;
&lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="na"&gt;run&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;npm run build&lt;/span&gt;
&lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="na"&gt;run&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;npx @bunny.net/cli scripts deploy dist/index.js ${{ secrets.SCRIPT_ID }}&lt;/span&gt;
  &lt;span class="na"&gt;env&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
    &lt;span class="na"&gt;BUNNYNET_API_KEY&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;${{ secrets.BUNNYNET_API_KEY }}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;When you scaffold with &lt;code&gt;bunny scripts init --deploy&lt;/code&gt;, the command prints the &lt;code&gt;SCRIPT_ID&lt;/code&gt; to add as a repo secret, so CI deploys to the right script without committing the link manifest.&lt;/p&gt;

&lt;p&gt;AI coding assistants use the CLI directly, either from a global install or through &lt;code&gt;npx @bunny.net/cli&lt;/code&gt;. We ship Edge Scripting skills alongside it, so Claude Code, Cursor, Windsurf, or any agent that runs shell commands can scaffold a project, link it, set environment variables, and deploy.&lt;/p&gt;

&lt;h2&gt;
  
  
  What's next
&lt;/h2&gt;

&lt;p&gt;Edge Scripting joins Bunny Database in the CLI today. Storage, Magic Containers, and the rest of the bunny.net stack are coming next.&lt;/p&gt;

&lt;p&gt;Get started and create your first Edge Script with the bunny.net CLI:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npm install -g @bunny.net/cli
bunny login
bunny scripts init
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The CLI is open source and developed in public. If something's broken, &lt;a href="https://github.com/BunnyWay/cli/issues" rel="noopener noreferrer"&gt;open an issue&lt;/a&gt;. If you want to share what you've built, find us in &lt;a href="https://discord.com/invite/bunnynet" rel="noopener noreferrer"&gt;Discord&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>javascript</category>
      <category>devops</category>
      <category>cli</category>
      <category>serverless</category>
    </item>
    <item>
      <title>Introducing the bunny.net CLI</title>
      <dc:creator>Jamie Barton</dc:creator>
      <pubDate>Mon, 09 Nov 2026 14:29:05 +0000</pubDate>
      <link>https://dev.to/bunnydotnet/introducing-the-bunnynet-cli-59np</link>
      <guid>https://dev.to/bunnydotnet/introducing-the-bunnynet-cli-59np</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published at bunny.net on May 11, 2026. Since then, the bunny.net CLI has expanded beyond Bunny Database. Find out more &lt;a href="https://bunny.net/docs/cli" rel="noopener noreferrer"&gt;in the docs&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;The best developer tools don't ask you to context-switch. They meet you where you already are.&lt;/p&gt;

&lt;p&gt;For most developers, that's the terminal. Not because it's retro or minimal, but because it's the one surface that works everywhere—your local machine, your CI pipeline, your AI coding assistant. The commands you type are the same commands your automation runs. A good CLI isn't just a power-user shortcut. It's the most composable interface a platform can offer.&lt;/p&gt;

&lt;p&gt;Today we're releasing the bunny.net CLI, a single command-line tool for building and managing your entire bunny.net stack. This first release ships with full Database support, including the interactive SQL shell we introduced a few weeks ago. Support for Edge Scripting, Storage, Magic Containers, and more is coming soon.&lt;/p&gt;

&lt;p&gt;The CLI is currently in public preview, and we’re building it in the open. We’d love your feedback, bug reports, and pull requests as we shape what comes next.&lt;/p&gt;

&lt;h2&gt;
  
  
  Up and running in three commands
&lt;/h2&gt;

&lt;p&gt;Install with npm:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;npm install -g @bunny.net/cli

# or
# curl -fsSL https://cli.bunny.net/install.sh | sh
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Log in:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;bunny login
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This opens your browser, authenticates with your bunny.net account, and saves a profile locally. Note that it currently fetches your API key from your account once signed in.&lt;/p&gt;

&lt;p&gt;Confirm it worked:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;bunny whoami
Logged in as Jamie Barton (jamie@bunny.net) 🐇
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fquab2ozg7ss7bib3g0ox.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fquab2ozg7ss7bib3g0ox.png" alt=" " width="799" height="649"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Database management without the dashboard detour
&lt;/h2&gt;

&lt;p&gt;The usual flow after creating a database is to open a dashboard, hunt for the connection string, copy it, paste it somewhere, hope you got the right one.&lt;/p&gt;

&lt;p&gt;The CLI replaces all of that with a few commands.&lt;/p&gt;

&lt;h3&gt;
  
  
  Create a database
&lt;/h3&gt;

&lt;p&gt;Run &lt;code&gt;bunny db create&lt;/code&gt; with no arguments and the CLI walks you through it interactively — name, region, options:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;bunny db create
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Already know what you want? Pass the flags directly:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;bunny db create &lt;span class="nt"&gt;--name&lt;/span&gt; my-app-db &lt;span class="nt"&gt;--primary&lt;/span&gt; UK
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Both paths produce the same result. Interactive mode is great for exploring. Flags-first is what you'll reach for in scripts, pipelines, or when your AI assistant is driving.&lt;/p&gt;

&lt;p&gt;After creation, the CLI offers to link the database to your current directory, generate an auth token, and write credentials to &lt;code&gt;.env&lt;/code&gt;  so you can go straight from &lt;code&gt;create&lt;/code&gt; to querying in the same shell session.&lt;/p&gt;

&lt;p&gt;Inspect what you just created:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;bunny db show

 Key               Value
 ID                db_01KP8D0MKHB7HWEYYE6VX8CTG7
 Name              my-app-db
 URL               libsql://01KP8D0MGVG0PEWR9SCTND02PH-my-app-db.lite.bunnydb.net/
 Status            Active    
 Size              4.1 KB / 1024.0 MB  ░░░░░░░░░░░░░░░░░░░░  0%
 Storage Region    eu-west-1                   
 Primary Region    London &lt;span class="o"&gt;(&lt;/span&gt;UK&lt;span class="o"&gt;)&lt;/span&gt;
 Replica Regions   None
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  Linking a directory to a database
&lt;/h3&gt;

&lt;p&gt;Most &lt;code&gt;db&lt;/code&gt; commands need to know which database you're targeting. Passing an ID every time gets old fast, so the CLI resolves the target database automatically in this order:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;An explicit &lt;code&gt;&amp;lt;database-id&amp;gt;&lt;/code&gt; argument&lt;/li&gt;
&lt;li&gt;A &lt;code&gt;.bunny/database.json&lt;/code&gt; manifest created by &lt;code&gt;bunny db link&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;BUNNY_DATABASE_URL&lt;/code&gt; from a &lt;code&gt;.env&lt;/code&gt; file (walked up from the current directory)&lt;/li&gt;
&lt;li&gt;An interactive picker if none of the above match&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The recommended flow is &lt;code&gt;bunny db link&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;bunny db &lt;span class="nb"&gt;link&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This writes a small &lt;code&gt;.bunny/database.json&lt;/code&gt; manifest to your project. Every &lt;code&gt;db&lt;/code&gt; command run from that directory (&lt;code&gt;show&lt;/code&gt;, &lt;code&gt;shell&lt;/code&gt;, &lt;code&gt;studio&lt;/code&gt;, &lt;code&gt;usage&lt;/code&gt;, &lt;code&gt;tokens create&lt;/code&gt;) now knows which database to target. No flags, no env var lookups, no connection strings in your shell history.&lt;/p&gt;

&lt;p&gt;Add &lt;code&gt;.bunny/&lt;/code&gt; to your &lt;code&gt;.gitignore&lt;/code&gt;. The manifest is a per-developer convenience, not something to commit. Each contributor links their own environment.&lt;/p&gt;

&lt;p&gt;If you'd rather drive things from &lt;code&gt;.env&lt;/code&gt; (handy when the same &lt;code&gt;BUNNY_DATABASE_URL&lt;/code&gt; is already wired into your app), the CLI picks that up automatically. And when you need to run a one-off command against a different database without changing context, pass the ID as an argument:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;bunny db show db_01KP8D0MKHB7HWEYYE6VX8CTG7
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  List, monitor, and clean up
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;bunny db list
bunny db delete
bunny db usage
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  Multi-region replication
&lt;/h3&gt;

&lt;p&gt;Bring data closer to your users with read replicas:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;bunny db regions list
bunny db regions add &lt;span class="nt"&gt;--replicas&lt;/span&gt; UK,NY
bunny db regions remove &lt;span class="nt"&gt;--replicas&lt;/span&gt; NY
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  Token management
&lt;/h3&gt;

&lt;p&gt;Generate and revoke database tokens without touching the dashboard:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;bunny db tokens create
bunny db tokens create &lt;span class="nt"&gt;--read-only&lt;/span&gt; &lt;span class="nt"&gt;--expiry&lt;/span&gt; 30d
bunny db tokens invalidate
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  Drop into the interactive shell
&lt;/h3&gt;

&lt;p&gt;The CLI embeds the same @bunny.net/database-shell we released as a standalone package, so you get the full interactive experience (dot-commands, saved views, output modes, sensitive column masking) with zero extra setup:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;bunny db shell
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;





&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;✓ Connected to database
  Type .help for commands, .quit to exit.

→  SELECT id, name, email FROM users;
┌────┬───────────┬─────────────────────┐
│ id │ name      │ email               │
├────┼───────────┼─────────────────────┤
│ 1  │ Alice     │ a****e@example.com  │
│ 2  │ Bob       │ b****b@example.com  │
└────┴───────────┴─────────────────────┘
2 rows (4ms)
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;No connection strings. No token flags. Your authenticated profile handles it. Just &lt;code&gt;bunny db shell&lt;/code&gt; and you're querying.&lt;/p&gt;

&lt;p&gt;Run a one-off query without entering the REPL:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;bunny db shell &amp;lt;database-id&amp;gt; &lt;span class="s2"&gt;"SELECT count(*) FROM orders"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  A read-only view with &lt;code&gt;bunny db studio&lt;/code&gt;
&lt;/h3&gt;

&lt;p&gt;Sometimes you don't want a REPL. You want to click through tables and see what's actually in there. &lt;code&gt;bunny db studio&lt;/code&gt; spins up a local server and opens a read-only table viewer in your browser:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;bunny db studio
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;It uses the same resolution order as every other &lt;code&gt;db&lt;/code&gt; command, so if you've run &lt;code&gt;bunny db link&lt;/code&gt; it picks up the right database automatically. A short-lived auth token is generated for the session and discarded when you close it.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fy7xgrj102udw6xr55rp9.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fy7xgrj102udw6xr55rp9.png" alt=" " width="800" height="437"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Studio is currently experimental and read-only by design, &lt;strong&gt;inspect, don't mutate&lt;/strong&gt;. For schema changes and data edits, reach for &lt;code&gt;bunny db shell&lt;/code&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Raw API access with &lt;code&gt;bunny api&lt;/code&gt;
&lt;/h2&gt;

&lt;p&gt;Purpose-built commands cover the most common workflows, but sometimes you need to reach an endpoint that doesn’t have a dedicated command yet, or you just want to poke at the API directly. That’s what &lt;code&gt;bunny api&lt;/code&gt; is for.&lt;/p&gt;

&lt;p&gt;It’s a raw, authenticated HTTP client for the entire bunny.net API. Pick a method, pass a path, and go:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight tsx"&gt;&lt;code&gt;&lt;span class="err"&gt;#&lt;/span&gt; &lt;span class="nx"&gt;List&lt;/span&gt; &lt;span class="nx"&gt;your&lt;/span&gt; &lt;span class="nx"&gt;pull&lt;/span&gt; &lt;span class="nx"&gt;zones&lt;/span&gt;
&lt;span class="nx"&gt;bunny&lt;/span&gt; &lt;span class="nx"&gt;api&lt;/span&gt; &lt;span class="nx"&gt;GET&lt;/span&gt; &lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="nx"&gt;pullzone&lt;/span&gt;

&lt;span class="err"&gt;#&lt;/span&gt; &lt;span class="nx"&gt;Grab&lt;/span&gt; &lt;span class="nx"&gt;a&lt;/span&gt; &lt;span class="nx"&gt;specific&lt;/span&gt; &lt;span class="nx"&gt;DNS&lt;/span&gt; &lt;span class="nx"&gt;zone&lt;/span&gt;
&lt;span class="nx"&gt;bunny&lt;/span&gt; &lt;span class="nx"&gt;api&lt;/span&gt; &lt;span class="nx"&gt;GET&lt;/span&gt; &lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="nx"&gt;dnszone&lt;/span&gt;&lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="mi"&gt;12345&lt;/span&gt;

&lt;span class="err"&gt;#&lt;/span&gt; &lt;span class="nx"&gt;Create&lt;/span&gt; &lt;span class="nx"&gt;a&lt;/span&gt; &lt;span class="nx"&gt;resource&lt;/span&gt; &lt;span class="kd"&gt;with&lt;/span&gt; &lt;span class="nx"&gt;a&lt;/span&gt; &lt;span class="nx"&gt;JSON&lt;/span&gt; &lt;span class="nx"&gt;body&lt;/span&gt;
&lt;span class="nx"&gt;bunny&lt;/span&gt; &lt;span class="nx"&gt;api&lt;/span&gt; &lt;span class="nx"&gt;POST&lt;/span&gt; &lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="nx"&gt;videolibrary&lt;/span&gt; &lt;span class="o"&gt;--&lt;/span&gt;&lt;span class="nx"&gt;body&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;{"Name":"uploads","ReplicationRegions":["DE","NY"]}&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Every request is automatically authenticated with your current profile, and every response is pretty-printed JSON by default. Pair it with &lt;code&gt;--output json&lt;/code&gt; and &lt;code&gt;jq&lt;/code&gt; to build quick one-liners:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight tsx"&gt;&lt;code&gt;&lt;span class="nx"&gt;bunny&lt;/span&gt; &lt;span class="nx"&gt;api&lt;/span&gt; &lt;span class="nx"&gt;GET&lt;/span&gt; &lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="nx"&gt;pullzone&lt;/span&gt; &lt;span class="o"&gt;--&lt;/span&gt;&lt;span class="nx"&gt;output&lt;/span&gt; &lt;span class="nx"&gt;json&lt;/span&gt; &lt;span class="o"&gt;|&lt;/span&gt; &lt;span class="nx"&gt;jq&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;.[].Name&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;You can also pipe request bodies from stdin, which makes it easy to compose with other tools or feed in generated payloads:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight tsx"&gt;&lt;code&gt;&lt;span class="nx"&gt;cat&lt;/span&gt; &lt;span class="nx"&gt;payload&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;json&lt;/span&gt; &lt;span class="o"&gt;|&lt;/span&gt; &lt;span class="nx"&gt;bunny&lt;/span&gt; &lt;span class="nx"&gt;api&lt;/span&gt; &lt;span class="nx"&gt;POST&lt;/span&gt; &lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="nx"&gt;dnszone&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Think of &lt;code&gt;bunny api&lt;/code&gt; as the escape hatch. If the bunny.net API supports it, you can call it from your terminal right now — no wrapper command needed, no dashboard required. It’s especially useful for AI agents that need to access endpoints beyond the built-in commands.&lt;/p&gt;

&lt;h2&gt;
  
  
  Built like the CLIs you already trust
&lt;/h2&gt;

&lt;p&gt;We followed the &lt;a href="https://clig.dev/" rel="noopener noreferrer"&gt;Command Line Interface Guidelines&lt;/a&gt; closely. The conventions that make &lt;code&gt;git&lt;/code&gt;, &lt;code&gt;docker&lt;/code&gt;, and &lt;code&gt;kubectl&lt;/code&gt; feel predictable - we wanted &lt;code&gt;bunny&lt;/code&gt; to feel that way from the start.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Interactive or scriptable - your call.&lt;/strong&gt; Prompts and spinners are TTY-aware. They show up in your terminal but stay out of the way in CI or when piping output.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Structured output everywhere.&lt;/strong&gt; Every command supports &lt;code&gt;--output json&lt;/code&gt;. Primary output goes to stdout, messages go to stderr, so piping always works cleanly:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;bunny db list &lt;span class="nt"&gt;--output&lt;/span&gt; json | jq &lt;span class="s1"&gt;'.[].name'&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Clear, helpful errors.&lt;/strong&gt; Errors are written in plain language with hints on how to fix them. Exit codes are meaningful: &lt;code&gt;1&lt;/code&gt; for fixable problems, &lt;code&gt;2&lt;/code&gt; for internal errors. With &lt;code&gt;--output json&lt;/code&gt;, errors come back as structured JSON too.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Respects your environment.&lt;/strong&gt; The CLI honors &lt;code&gt;NO_COLOR&lt;/code&gt;, supports named profiles for switching between accounts, and reads &lt;code&gt;BUNNYNET_API_KEY&lt;/code&gt; from your environment when you'd rather skip interactive login:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;bunny config profile create &lt;span class="nt"&gt;--name&lt;/span&gt; work
bunny login &lt;span class="nt"&gt;--profile&lt;/span&gt; work
bunny db list &lt;span class="nt"&gt;--profile&lt;/span&gt; work
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Your AI agent already knows how to use it
&lt;/h2&gt;

&lt;p&gt;There's a growing question in the developer tools space: do AI agents need custom protocols, or are the CLI tools developers already use enough?&lt;/p&gt;

&lt;p&gt;Increasingly, the answer is that CLIs win.&lt;/p&gt;

&lt;p&gt;AI models have been trained on billions of lines of terminal interactions. When an agent reaches for a CLI, it's drawing on deeply learned patterns, not adapting to a bespoke integration. Every bunny CLI command that returns structured JSON is a command an AI agent can already use, with zero extra setup.&lt;/p&gt;

&lt;p&gt;If you're working with Claude Code, Cursor, or Windsurf, your assistant can already create databases, manage tokens, and query data through the bunny CLI,  the same way it uses &lt;code&gt;git&lt;/code&gt; or &lt;code&gt;npm&lt;/code&gt; today. No MCP server to configure. No schema tokens eating your context window. The CLI you use is the same interface your agent uses.&lt;/p&gt;

&lt;p&gt;The CLI comes with agent skills for databases and scripts so your agent knows how to get started. Below we can see Claude Code discovered the tool, skills, and created a database and schema for a new project.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F6fokvlbk9q50cny05a3s.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F6fokvlbk9q50cny05a3s.png" alt=" " width="800" height="920"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What's coming next
&lt;/h2&gt;

&lt;p&gt;Database support is the starting point. Here's where we're headed.&lt;/p&gt;

&lt;h3&gt;
  
  
  Edge Scripting
&lt;/h3&gt;

&lt;p&gt;Scaffold a project, deploy serverless functions to the edge, and manage secrets, all from the terminal. Deployment history and rollbacks are on the roadmap too.&lt;/p&gt;

&lt;h3&gt;
  
  
  Storage
&lt;/h3&gt;

&lt;p&gt;Create buckets, list and sync files, and manage access to S3-compatible storage. The same operations you'd do in the dashboard or with a third-party client, built directly into the CLI with your existing auth.&lt;/p&gt;

&lt;h3&gt;
  
  
  Magic Containers Apps
&lt;/h3&gt;

&lt;p&gt;If you've ever wanted to go from a &lt;code&gt;Dockerfile&lt;/code&gt; to a running, globally distributed application in a single command, that's what we’re adding next.&lt;/p&gt;

&lt;h3&gt;
  
  
  The bigger picture
&lt;/h3&gt;

&lt;p&gt;Our goal is a workflow where you go from an empty directory to a fully deployed application without leaving the terminal. Database provisioned, edge functions live, storage configured, containers scaled. Whether you're typing the commands or your AI assistant is running them, it's the same tool, the same output, the same interface.&lt;/p&gt;

&lt;p&gt;Every bunny.net product, one CLI.&lt;/p&gt;

&lt;h2&gt;
  
  
  Built in the open, built in TypeScript
&lt;/h2&gt;

&lt;p&gt;The bunny CLI is open source, and we’re developing it in public. This isn’t a finished product we’re handing to developers. It’s an active project we want to build with you. &lt;/p&gt;

&lt;p&gt;The bunny.net developer platform is JavaScript-native. Edge Scripts run with Deno and Node.js compatibility. The developers building on bunny.net write JavaScript and TypeScript. By keeping the CLI in the same language, we can share code between the CLI and the scripts developers write. Use exports, generated clients, and utilities written for the CLI inside Edge Scripts. &lt;/p&gt;

&lt;p&gt;One language for the CLI, the API client, the config schemas, and the edge runtime means fewer switches and a codebase that any JS developer can read, debug, or contribute to. &lt;/p&gt;

&lt;p&gt;If something is broken, &lt;a href="https://github.com/BunnyWay/cli/issues" rel="noopener noreferrer"&gt;open an issue&lt;/a&gt;. If you want a feature, tell us. If you want to contribute, pull requests are welcome. The CLI is built with TypeScript, Yargs, and a lot of packages that should feel very familiar.&lt;/p&gt;

&lt;h2&gt;
  
  
  Get started
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npm &lt;span class="nb"&gt;install&lt;/span&gt; &lt;span class="nt"&gt;-g&lt;/span&gt; @bunny.net/cli
bunny login
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;a href="https://github.com/bunnyWay/cli" rel="noopener noreferrer"&gt;Star the repo on GitHub&lt;/a&gt;, join us on &lt;a href="https://discord.com/invite/bunnynet" rel="noopener noreferrer"&gt;Discord&lt;/a&gt;, and let’s build this together.&lt;/p&gt;

</description>
      <category>cli</category>
      <category>devtools</category>
      <category>database</category>
      <category>devops</category>
    </item>
    <item>
      <title>I published my first WordPress plugin, twenty years after my last one</title>
      <dc:creator>Jamie Barton</dc:creator>
      <pubDate>Fri, 30 Oct 2026 15:41:55 +0000</pubDate>
      <link>https://dev.to/notrab/i-published-my-first-wordpress-plugin-twenty-years-after-my-last-one-4g57</link>
      <guid>https://dev.to/notrab/i-published-my-first-wordpress-plugin-twenty-years-after-my-last-one-4g57</guid>
      <description>&lt;p&gt;Twenty years ago I had a few dev plugins I'd drop onto client sites. None of them ever went near WordPress.org. I'd never submitted a plugin for review, never touched the plugin directory's SVN repository, and the thought of doing both for &lt;a href="https://orbitwrite.com" rel="noopener noreferrer"&gt;Orbitwrite&lt;/a&gt; made me nervous.&lt;/p&gt;

&lt;p&gt;This month the Orbitwrite plugin went live on &lt;a href="https://wordpress.org/plugins/orbitwrite" rel="noopener noreferrer"&gt;WordPress.org&lt;/a&gt;. I built it with Claude, and Claude did most of the heavy lifting.&lt;/p&gt;

&lt;p&gt;The brief was a sentence: write the social post for an article inside WordPress, then schedule it or send it now through Orbitwrite. A lot of WordPress has changed since I last wrote a plugin. The block editor didn't exist, so the sidebar is new territory for me, and Claude wrote it in TypeScript with &lt;code&gt;wp-scripts&lt;/code&gt;, then mounted the same composer as a box for sites still on the Classic Editor.&lt;/p&gt;

&lt;p&gt;Connecting came next. Each WordPress user signs in to their own Orbitwrite account over OAuth, so nobody pastes an API key into a settings page everyone shares. Orbitwrite registers OAuth clients by CIMD, where the client id is a URL to a small JSON document describing the client, and each site serves its own at &lt;code&gt;/wp-json/orbitwrite/v1/oauth-client&lt;/code&gt;. That only works on a public HTTPS site with pretty permalinks, so the plugin checks for both and says which to fix before sending anyone off to sign in.&lt;/p&gt;

&lt;p&gt;Then the refresh tokens!! Ours rotate, so each one works once, and the block editor fires several requests at the same moment. Two requests that both find an expired token both try to spend it, and the loser disconnects you. &lt;code&gt;add_option()&lt;/code&gt; reads and then upserts, so two requests can both take a lock built on it. The plugin takes its lock with a plain &lt;code&gt;INSERT IGNORE&lt;/code&gt; on &lt;code&gt;wp_options&lt;/code&gt;, which is the kind of WordPress detail I'd never have found on my own.&lt;/p&gt;

&lt;p&gt;Images were next.... Bluesky caps an image at 2 MB, X at 5 MB and Instagram at 8 MB, and Orbitwrite refuses an image over the cap. WordPress has already generated a pile of sizes for every upload, so the plugin sends each network the largest one with the same shape that it accepts.&lt;/p&gt;

&lt;p&gt;The part that calmed my nerves was the tests. CI runs PHPCS with the WordPress-Extra rules, a PHP 7.4 job for the oldest version the plugin supports, and an end-to-end run that builds a throwaway WordPress on SQLite with a mock Orbitwrite and clicks through connecting, scheduling and auto-share in Chromium. A weekly job checks the slice of Orbitwrite's OpenAPI spec the plugin calls against the live one, so an API change shows up in CI before it shows up for a user. The plugin also passed WordPress's own Plugin Check before I submitted it.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ffyelel6104ysjgqnytfk.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ffyelel6104ysjgqnytfk.webp" alt="Editor" width="800" height="572"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;My part was a few forms on WordPress.org and the deploy. That's a GitHub Action using &lt;code&gt;10up/action-wordpress-plugin-deploy&lt;/code&gt;, with my SVN username and password saved as repository secrets, which made me shiver. Pushing a tag like &lt;code&gt;v0.2.0&lt;/code&gt; checks the tag matches the plugin header, the version constant and the readme's Stable tag, builds the plugin and copies it into the SVN repository's &lt;code&gt;trunk&lt;/code&gt; and &lt;code&gt;tags/0.2.0&lt;/code&gt;. A second workflow pushes banners, screenshots and readme edits to the plugin page whenever they change on &lt;code&gt;main&lt;/code&gt;, so I never open SVN at all.&lt;/p&gt;

&lt;p&gt;If you've got an old plugin sitting in a client's &lt;code&gt;wp-content&lt;/code&gt; folder, it's a few forms and a tag away from WordPress.org. Ours is &lt;a href="https://wordpress.org/plugins/orbitwrite" rel="noopener noreferrer"&gt;Orbitwrite&lt;/a&gt;, and it shares your next article for you.&lt;/p&gt;

</description>
      <category>showdev</category>
      <category>claude</category>
      <category>php</category>
      <category>wordpress</category>
    </item>
    <item>
      <title>A Buffer clone is a cron job and a pile of OAuth apps</title>
      <dc:creator>Jamie Barton</dc:creator>
      <pubDate>Thu, 29 Oct 2026 17:22:00 +0000</pubDate>
      <link>https://dev.to/notrab/a-buffer-clone-is-a-cron-job-and-a-pile-of-oauth-apps-18kh</link>
      <guid>https://dev.to/notrab/a-buffer-clone-is-a-cron-job-and-a-pile-of-oauth-apps-18kh</guid>
      <description>&lt;p&gt;When we started building &lt;a href="https://orbitwrite.com" rel="noopener noreferrer"&gt;Orbitwrite&lt;/a&gt;, I thought a Buffer clone was a cron job and a handful of OAuth apps. You keep a &lt;code&gt;posts&lt;/code&gt; table with a &lt;code&gt;scheduled_at&lt;/code&gt; column, run a job every minute and call each network's API when a row comes due! 🤣&lt;/p&gt;

&lt;p&gt;The cron job was the easy bit for the PoC. Everything else arrived one network at a time.&lt;/p&gt;

&lt;p&gt;Most networks want their own OAuth app, their own review process and their own idea of how a refresh token behaves. Each one is a small project, and none of them finish when the first post goes out, because tokens expire, scopes change and someone always needs to reconnect.&lt;/p&gt;

&lt;p&gt;Media came next.... TikTok refuses video under 23 frames per second, so a 15 FPS screen recording looks fine when you schedule it and fails when the job runs, hours after you've stopped thinking about it. Every network has a handful of rules like that, and I want a post to tell me about them while I'm still writing it.&lt;/p&gt;

&lt;p&gt;Then the quotas!! LinkedIn gives one app a small daily allowance that every connected account shares, and X bills reads by the call, so checking for replies has a price you plan around. A thread that fails on its third post has already published the first two, and a publish that timed out may have gone through before the connection dropped, so retrying it posts the same thing twice.&lt;/p&gt;

&lt;p&gt;That's most of what Orbitwrite is today. It publishes to X, LinkedIn, Bluesky, Mastodon, Threads, Instagram, Facebook, TikTok, YouTube, Discord, Slack and Telegram, and the web app is one client of a public API. The CLI, the SDK and an MCP server are the others. They all run through the same permission checks, platform limits and approvals, so a post from a script behaves like one from the app.&lt;/p&gt;

&lt;p&gt;The CLI is the shortest path: &lt;code&gt;npx @orbitwrite/cli post "Shipped it." --all --next&lt;/code&gt; sends a post to every channel at the next free slot in your schedule.&lt;/p&gt;

&lt;p&gt;The MCP server is the one I'd point most people at. Add &lt;code&gt;https://mcp.orbitwrite.com/mcp&lt;/code&gt; to Claude or ChatGPT as a custom connector, sign in, and ask for the work in plain words: draft a post about the new docs for each channel, score it, and suggest the next free time. The agent has over a hundred tools and sees your channels by name and handle, with the tokens behind them kept on our servers. It follows the same approvals your team does, so a member who needs sign-off to publish can only schedule behind a review.&lt;/p&gt;

&lt;p&gt;If you're halfway through your own scheduler, keep the cron job. Point it at the &lt;a href="https://orbitwrite.com/docs/developers" rel="noopener noreferrer"&gt;API&lt;/a&gt; and let us look after the OAuth apps.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>mcp</category>
      <category>api</category>
      <category>showdev</category>
    </item>
    <item>
      <title>Top 5 tools every frontend developer should be using with GraphQL in 2023</title>
      <dc:creator>Jamie Barton</dc:creator>
      <pubDate>Wed, 31 May 2023 08:33:01 +0000</pubDate>
      <link>https://dev.to/grafbase/top-5-tools-every-frontend-developer-should-be-using-with-graphql-in-2023-5gj3</link>
      <guid>https://dev.to/grafbase/top-5-tools-every-frontend-developer-should-be-using-with-graphql-in-2023-5gj3</guid>
      <description>&lt;p&gt;Every week, a bunch of fresh tools, services, and libraries make their debut, claiming to take the GraphQL developer experience to the next level.&lt;/p&gt;

&lt;p&gt;  &lt;iframe src="https://www.youtube.com/embed/AV4Amf3Mag0" width="710" height="399"&gt;
  &lt;/iframe&gt;
&lt;/p&gt;

&lt;p&gt;Here are my top 5 tools every frontend developer should be using with GraphQL in 2023:&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Grafbase OpenAPI Connector
&lt;/h2&gt;

&lt;p&gt;Maximize the power of web and mobile app development by effortlessly blending REST and GraphQL APIs with Grafbase. Say goodbye to complexity and hello to a unified GraphQL API that supercharges your app development process.&lt;/p&gt;

&lt;p&gt;Enter &lt;a href="https://en.wikipedia.org/wiki/OpenAPI_Specification" rel="noopener noreferrer"&gt;OpenAPI&lt;/a&gt;, formerly known as Swagger - the ultimate game-changer for API definition and documentation. It simplifies things by describing APIs in a format that machines understand, making it easier for developers to work with all kinds of APIs. And with &lt;a href="https://grafbase.com/edge-gateway" rel="noopener noreferrer"&gt;Grafbase Edge Gateway&lt;/a&gt;, you can seamlessly merge OpenAPI-driven REST APIs and transform them into GraphQL, taking your stack to a whole new level of awesomeness.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight graphql"&gt;&lt;code&gt;&lt;span class="k"&gt;extend&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="k"&gt;schema&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="err"&gt;@&lt;/span&gt;&lt;span class="n"&gt;openapi&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="n"&gt;name&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="err"&gt;"&lt;/span&gt;&lt;span class="n"&gt;Stripe&lt;/span&gt;&lt;span class="err"&gt;"&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="n"&gt;schema&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="err"&gt;"&lt;/span&gt;&lt;span class="n"&gt;https&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="err"&gt;//&lt;/span&gt;&lt;span class="n"&gt;raw&lt;/span&gt;&lt;span class="err"&gt;.&lt;/span&gt;&lt;span class="n"&gt;githubusercontent&lt;/span&gt;&lt;span class="err"&gt;.&lt;/span&gt;&lt;span class="n"&gt;com&lt;/span&gt;&lt;span class="err"&gt;/&lt;/span&gt;&lt;span class="n"&gt;stripe&lt;/span&gt;&lt;span class="err"&gt;/&lt;/span&gt;&lt;span class="n"&gt;openapi&lt;/span&gt;&lt;span class="err"&gt;/&lt;/span&gt;&lt;span class="n"&gt;master&lt;/span&gt;&lt;span class="err"&gt;/&lt;/span&gt;&lt;span class="n"&gt;openapi&lt;/span&gt;&lt;span class="err"&gt;/&lt;/span&gt;&lt;span class="n"&gt;spec3&lt;/span&gt;&lt;span class="err"&gt;.&lt;/span&gt;&lt;span class="n"&gt;json&lt;/span&gt;&lt;span class="err"&gt;"&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="n"&gt;headers&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="w"&gt;
      &lt;/span&gt;&lt;span class="err"&gt;{&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;name&lt;/span&gt;&lt;span class="err"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="err"&gt;"&lt;/span&gt;&lt;span class="n"&gt;Authorization&lt;/span&gt;&lt;span class="err"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;value&lt;/span&gt;&lt;span class="err"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="err"&gt;"&lt;/span&gt;&lt;span class="n"&gt;Bearer&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="err"&gt;{{&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;env&lt;/span&gt;&lt;span class="err"&gt;.&lt;/span&gt;&lt;span class="n"&gt;STRIPE_API_KEY&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="err"&gt;}}"&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="err"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="n"&gt;query&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;Query&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;It's free to get started and you don't even need an account to build locally:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npx grafbase init &lt;span class="nt"&gt;--template&lt;/span&gt; openapi-stripe
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  2. GraphQL Code Generator — Client Preset
&lt;/h2&gt;

&lt;p&gt;The type system in GraphQL is a major game-changer. We can leverage the GraphQL Code Generator to use that same type system to generate TypeScript types so we can build better frontends without error.&lt;/p&gt;

&lt;p&gt;In the past, we relied on the GraphQL Code Generator to generate hooks for our existing GraphQL clients. But it was a pain when we wanted to switch to new clients.&lt;/p&gt;

&lt;p&gt;The GraphQL Code Generator recommends using the &lt;a href="https://the-guild.dev/graphql/codegen/plugins/presets/preset-client" rel="noopener noreferrer"&gt;&lt;code&gt;client-preset&lt;/code&gt;&lt;/a&gt; and &lt;a href="https://the-guild.dev/graphql/codegen/plugins/typescript/typed-document-node" rel="noopener noreferrer"&gt;&lt;code&gt;TypedDocumentNode&lt;/code&gt;&lt;/a&gt; to level up our functions and make sure we're getting the correct operation and variable types.&lt;/p&gt;

&lt;p&gt;Plus, it's all about keeping operations and fragments in their own components. This approach reduces code complexity, keeps things tidy, and makes it a breeze to switch to any GraphQL client that supports &lt;code&gt;TypedDocumentNode&lt;/code&gt;.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight tsx"&gt;&lt;code&gt;&lt;span class="k"&gt;export&lt;/span&gt; &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;LessonFragment&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nf"&gt;graphql&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="cm"&gt;/* GraphQL */&lt;/span&gt; &lt;span class="s2"&gt;`
  fragment LessonItem on Lesson {
    title
  }
`&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;

&lt;span class="k"&gt;export&lt;/span&gt; &lt;span class="kd"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;Lesson&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;props&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;lesson&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;FragmentType&lt;/span&gt;&lt;span class="o"&gt;&amp;lt;&lt;/span&gt;&lt;span class="k"&gt;typeof&lt;/span&gt; &lt;span class="nx"&gt;LessonFragment&lt;/span&gt;&lt;span class="o"&gt;&amp;gt;&lt;/span&gt; &lt;span class="p"&gt;})&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;lesson&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nf"&gt;useFragment&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;LessonFragment&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;props&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;lesson&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;

  &lt;span class="k"&gt;return &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;
    &lt;span class="c1"&gt;// Fully typed!&lt;/span&gt;
    &lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nt"&gt;li&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;&lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="nx"&gt;lesson&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;title&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt;&lt;span class="p"&gt;&amp;lt;/&lt;/span&gt;&lt;span class="nt"&gt;li&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
  &lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  3. GQty
&lt;/h2&gt;

&lt;p&gt;Are you tired of the hassle of writing GraphQL operations and configuring codegen for TypeScript? Say goodbye to all that and switch to &lt;a href="https://gqty.dev/" rel="noopener noreferrer"&gt;GQty&lt;/a&gt;!&lt;/p&gt;

&lt;p&gt;With GQty, you don't even need a separate GraphQL client. It's like magic! GQty takes care of transforming your code into a GraphQL operation behind the scenes. So sit back, relax, and let GQty handle all the heavy lifting for you.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight tsx"&gt;&lt;code&gt;&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="kd"&gt;type&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;FunctionComponent&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;react&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;
&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;useQuery&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;../gqty/&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;

&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;Query&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;FunctionComponent&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;()&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="na"&gt;me&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;name&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;friends&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nf"&gt;useQuery&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt;

  &lt;span class="k"&gt;return &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;
    &lt;span class="p"&gt;&amp;lt;&amp;gt;&lt;/span&gt;
      Hello &lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="nx"&gt;name&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt;!
      &lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nt"&gt;ol&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
        &lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="nf"&gt;friends&lt;/span&gt;&lt;span class="p"&gt;().&lt;/span&gt;&lt;span class="nf"&gt;map&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;user&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;
          &lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nt"&gt;li&lt;/span&gt; &lt;span class="na"&gt;key&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="nx"&gt;user&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;id&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;&lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="nx"&gt;user&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;name&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt;&lt;span class="p"&gt;&amp;lt;/&lt;/span&gt;&lt;span class="nt"&gt;li&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
        &lt;span class="p"&gt;))&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt;
      &lt;span class="p"&gt;&amp;lt;/&lt;/span&gt;&lt;span class="nt"&gt;ol&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
    &lt;span class="p"&gt;&amp;lt;/&amp;gt;&lt;/span&gt;
  &lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="k"&gt;export&lt;/span&gt; &lt;span class="k"&gt;default&lt;/span&gt; &lt;span class="nx"&gt;Query&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  4. GraphQL Network Inspector
&lt;/h2&gt;

&lt;p&gt;The days of struggling to identify &lt;code&gt;/graphql&lt;/code&gt; requests in the Network Inspector are over!&lt;/p&gt;

&lt;p&gt;&lt;a href="https://github.com/warrenday/graphql-network-inspector" rel="noopener noreferrer"&gt;GraphQL Network Inspector&lt;/a&gt;, an awesome extension for developer tools that makes debugging a breeze. &lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F4fkyrn7rqj9f5sji90j1.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F4fkyrn7rqj9f5sji90j1.png" alt="GraphQL Network Inspector" width="800" height="502"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;It categorizes requests into queries, mutations, and subscriptions and even uses the GraphQL operation name. Say goodbye to confusion and hello to simplified debugging.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. GraphMan
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://github.com/Escape-Technologies/graphman" rel="noopener noreferrer"&gt;GraphMan&lt;/a&gt; takes away all the boring and time-consuming aspects of crafting queries and mutations for a GraphQL API. &lt;/p&gt;

&lt;p&gt;With GraphMan, you can effortlessly generate a comprehensive collection from a single GraphQL endpoint. Each collection includes requests for every query and mutation, all conveniently pre-filled variables.&lt;/p&gt;

&lt;p&gt;To create a collection, just pass your Grafbase API URL to the command below. It's that easy!&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;deno run https://deno.land/x/graphman@v1.2.1/src/cli.ts GRAFBASE_API_URL_HERE
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  &amp;nbsp;Join us at GraphQL Conf
&lt;/h2&gt;

&lt;p&gt;Do you want to learn more about GraphQL? Join us at GraphQL Conf this year. &lt;a href="https://graphql.org/conf/" rel="noopener noreferrer"&gt;Get your tickets now&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>graphql</category>
      <category>tooling</category>
      <category>beginners</category>
    </item>
    <item>
      <title>Grafbase Public Beta</title>
      <dc:creator>Jamie Barton</dc:creator>
      <pubDate>Mon, 24 Apr 2023 08:44:38 +0000</pubDate>
      <link>https://dev.to/grafbase/grafbase-public-beta-2bi0</link>
      <guid>https://dev.to/grafbase/grafbase-public-beta-2bi0</guid>
      <description>&lt;p&gt;Grafbase is now in Public Beta!&lt;/p&gt;

&lt;p&gt;Since launching the &lt;a href="https://grafbase.com/blog/announcing-grafbase" rel="noopener noreferrer"&gt;Private Beta&lt;/a&gt; in July 2022, thousands of early adopters have joined our growing community to help shape and improve the Grafbase platform.&lt;/p&gt;

&lt;p&gt;&lt;iframe class="tweet-embed" id="tweet-1650416869927534592-347" src="https://platform.twitter.com/embed/Tweet.html?id=1650416869927534592"&gt;
&lt;/iframe&gt;

  // Detect dark theme
  var iframe = document.getElementById('tweet-1650416869927534592-347');
  if (document.body.className.includes('dark-theme')) {
    iframe.src = "https://platform.twitter.com/embed/Tweet.html?id=1650416869927534592&amp;amp;theme=dark"
  }



&lt;/p&gt;

&lt;p&gt;The core feature of the Grafbase platform is the &lt;a href="https://grafbase.com/edge-gateway" rel="noopener noreferrer"&gt;Edge Gateway&lt;/a&gt;, a programmable realtime GraphQL API deployed to the edge.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>programming</category>
      <category>api</category>
      <category>graphql</category>
    </item>
    <item>
      <title>Grafbase January 2023 Update</title>
      <dc:creator>Jamie Barton</dc:creator>
      <pubDate>Thu, 02 Feb 2023 14:06:25 +0000</pubDate>
      <link>https://dev.to/grafbase/grafbase-january-2023-update-58g4</link>
      <guid>https://dev.to/grafbase/grafbase-january-2023-update-58g4</guid>
      <description>&lt;p&gt;Hey &lt;strong&gt;Dev.to&lt;/strong&gt;!&lt;/p&gt;

&lt;p&gt;We are thrilled to share with you all of the latest product updates, resources, and a preview of what we’re working on next. &lt;/p&gt;

&lt;p&gt;Let’s get right to it…&lt;/p&gt;

&lt;h3&gt;
  
  
  Product Updates
&lt;/h3&gt;

&lt;p&gt;January has been an exciting month packed with lots of feature updates. &lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;&lt;a href="https://grafbase.com/blog/simplify-building-realtime-applications-with-graphql-live-queries" rel="noopener noreferrer"&gt;Live Queries&lt;/a&gt;&lt;/strong&gt;
Grafbase becomes the first hosted GraphQL platform to provide Live Queries. GraphQL Live Queries enable developers to build and deploy realtime apps with ease.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;a href="https://grafbase.com/roadmap" rel="noopener noreferrer"&gt;Product Roadmap&lt;/a&gt;&lt;/strong&gt;
Since launching the private beta last year, users have been asking about the future of Grafbase product roadmap. We’re super excited to share the public roadmap that you can follow, and even upvote features to be worked on first!&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;a href="https://grafbase.com/examples" rel="noopener noreferrer"&gt;Examples Directory&lt;/a&gt;&lt;/strong&gt;
With new examples being created every week we have made it even easier to find the example you’re looking for.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;a href="https://grafbase.com/guides" rel="noopener noreferrer"&gt;Guides Directory&lt;/a&gt;&lt;/strong&gt;
Learn how to build the next generation of web and mobile apps with new guides added every week!&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;You can see what’s new even quicker by following us on &lt;a href="https://twitter.com/grafbase" rel="noopener noreferrer"&gt;Twitter&lt;/a&gt;, browsing the &lt;a href="https://grafbase.com/changelog" rel="noopener noreferrer"&gt;changelog&lt;/a&gt;, or joining our &lt;a href="https://discord.com/invite/grafbase" rel="noopener noreferrer"&gt;Discord server&lt;/a&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  Resource Updates
&lt;/h3&gt;

&lt;p&gt;Also in January, there were lots of new documentation, guides, videos, tutorials, and code examples. &lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;&lt;a href="https://www.youtube.com/watch?v=YsFwI7H1iWM" rel="noopener noreferrer"&gt;[VIDEO]: Serverless GraphQL API with Grafbase by Simon Grimm&lt;/a&gt;&lt;/strong&gt;
Learn how to build a mobile application from scratch using Ionic with popular YouTuber Simon Grimm.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;a href="https://github.com/grafbase/playground/tree/main/packages/grafbase-urql-exchange" rel="noopener noreferrer"&gt;[PLUGIN]: URQL Exchange for Live Queries&lt;/a&gt;&lt;/strong&gt;
To celebrate the launch of Live Queries we made it even easier so developers don’t need to mess around configuring SSE. Install the custom URQL exchange and go!&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;a href="https://github.com/grafbase/playground/tree/main/packages/grafbase-apollo-link" rel="noopener noreferrer"&gt;[PLUGIN]: Apollo Link for Live Queries&lt;/a&gt;&lt;/strong&gt;
We also made it easier for developers using Apollo Client to get going with Live Queries. Add the custom Apollo Link by Grafbase and go!&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;a href="https://github.com/grafbase/grafbase/tree/main/examples/qwik" rel="noopener noreferrer"&gt;[EXAMPLE]: Qwik + Qwik City&lt;/a&gt;&lt;/strong&gt;
Everyone is talking about how “Qwik” this new framework is so Heather created an example to show how you can fetch data with GraphQL with Qwik City.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;a href="https://grafbase.com/guides/build-your-own-low-code-graphql-admin-ui-with-retool" rel="noopener noreferrer"&gt;[GUIDE]: Build your own low-code GraphQL Admin UI with Retool&lt;/a&gt;&lt;/strong&gt;
In this guide, Jamie shows how you can build your own Admin UI to manage Grafbase content using Retool.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;a href="https://grafbase.com/guides/working-with-eleventy-and-graphql" rel="noopener noreferrer"&gt;[GUIDE]: Working with Eleventy and GraphQL&lt;/a&gt;&lt;/strong&gt;
In this guide, Jamie shows how you can use the popular Static Site Generator Eleventy with GraphQL to fetch data from Grafbase.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;a href="https://dropjs.com/Building-GraphQL-Backends-with-SDL?notify-me" rel="noopener noreferrer"&gt;[WORKSHOP]: Building GraphQL Backends with SDL&lt;/a&gt;&lt;/strong&gt;
In this weekly JS Drop by This Dot Labs, Jamie releases a video on you build a GraphQL backend with Grafbase using SDL.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  What’s next?
&lt;/h3&gt;

&lt;p&gt;We’re working on lots of new features, including a new directive that lets you write your own resolvers, as well as CLI deploys, data explorer, and much more.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;That’s it for January!&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;PS. If you like what we’re building we’d love to hear more about what you think. Join us on &lt;a href="https://discord.gg/grafbase" rel="noopener noreferrer"&gt;Discord&lt;/a&gt;, &lt;a href="https://twitter.com/grafbase" rel="noopener noreferrer"&gt;Twitter&lt;/a&gt;, &lt;a href="https://youtube.com/@grafbase" rel="noopener noreferrer"&gt;YouTube&lt;/a&gt;, and &lt;a href="https://github.com/grafbase" rel="noopener noreferrer"&gt;GitHub&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>graphql</category>
      <category>backend</category>
      <category>webdev</category>
      <category>javascript</category>
    </item>
    <item>
      <title>Build realtime GraphQL backends with Grafbase</title>
      <dc:creator>Jamie Barton</dc:creator>
      <pubDate>Mon, 16 Jan 2023 16:01:35 +0000</pubDate>
      <link>https://dev.to/grafbase/build-realtime-graphql-backends-with-grafbase-3bpl</link>
      <guid>https://dev.to/grafbase/build-realtime-graphql-backends-with-grafbase-3bpl</guid>
      <description>&lt;p&gt;There are developers who don't want the hassle of building a backend, managing deployments, configuring continuous integration, juggling connection pooling, and more. &lt;/p&gt;

&lt;p&gt;&lt;a href="https://grafbase.com" rel="noopener noreferrer"&gt;Grafbase&lt;/a&gt; was built to manage all of the above. You get a distributed GraphQL API at the edge by creating a single &lt;code&gt;grafbase/schema.graphql&lt;/code&gt; file in your project.&lt;/p&gt;

&lt;p&gt;Your schema contains models with special directives to relate data, set default values, validation, and more.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight graphql"&gt;&lt;code&gt;&lt;span class="c"&gt;# grafbase/schema.graphql&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="k"&gt;type&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;Post&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="err"&gt;@&lt;/span&gt;&lt;span class="n"&gt;model&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="n"&gt;title&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nb"&gt;String&lt;/span&gt;&lt;span class="p"&gt;!&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="n"&gt;slug&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nb"&gt;String&lt;/span&gt;&lt;span class="p"&gt;!&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="err"&gt;@&lt;/span&gt;&lt;span class="n"&gt;unique&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;In 2021, &lt;a href="https://twitter.com/n1rual" rel="noopener noreferrer"&gt;Laurin Quast&lt;/a&gt; introduced a collection of packages to support the use of GraphQL Live Queries on the server and client.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Today, Grafbase is happy to announce it now supports GraphQL Live Queries!&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;This means that all you need to do to start using GraphQL Live Queries is add &lt;code&gt;@live&lt;/code&gt; to your query!&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight graphql"&gt;&lt;code&gt;&lt;span class="k"&gt;query&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="k"&gt;@live&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="n"&gt;postCollection&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;first&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;10&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="n"&gt;edges&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
      &lt;/span&gt;&lt;span class="n"&gt;node&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
        &lt;/span&gt;&lt;span class="n"&gt;id&lt;/span&gt;&lt;span class="w"&gt;
        &lt;/span&gt;&lt;span class="n"&gt;title&lt;/span&gt;&lt;span class="w"&gt;
      &lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The &lt;code&gt;@live&lt;/code&gt; directive will observe any changes to the data and send a message using &lt;a href="https://grafbase.com/docs/realtime/live-queries#server-sent-events" rel="noopener noreferrer"&gt;Server-Sent Events&lt;/a&gt; with the patch to update the current query state.&lt;/p&gt;

&lt;p&gt;The event is in the format of &lt;a href="https://grafbase.com/docs/realtime/live-queries#json-patch" rel="noopener noreferrer"&gt;JSON Patch&lt;/a&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"patch"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
      &lt;/span&gt;&lt;span class="nl"&gt;"op"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"add"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
      &lt;/span&gt;&lt;span class="nl"&gt;"path"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"/postCollection/edges/3"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
      &lt;/span&gt;&lt;span class="nl"&gt;"value"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
        &lt;/span&gt;&lt;span class="nl"&gt;"node"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
          &lt;/span&gt;&lt;span class="nl"&gt;"id"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"post_01GJMDWJ2M6WWTM26S7C1KKYBE"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
          &lt;/span&gt;&lt;span class="nl"&gt;"title"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"Instant serverless GraphQL backends"&lt;/span&gt;&lt;span class="w"&gt;
        &lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
      &lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="p"&gt;],&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"revision"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Together with &lt;a href="https://the-guild.dev/" rel="noopener noreferrer"&gt;The Guild&lt;/a&gt;, Grafbase is also releasing 2 new packages (with more on the way) to further abstract the effort needed to implement Live Queries on the frontend.&lt;/p&gt;

&lt;p&gt;Starting with support for &lt;a href="https://www.apollographql.com/docs/react/" rel="noopener noreferrer"&gt;Apollo Client&lt;/a&gt; and &lt;a href="https://formidable.com/open-source/urql/" rel="noopener noreferrer"&gt;URQL&lt;/a&gt;, you can add Live Queries with the following packages:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.npmjs.com/package/@grafbase/apollo-link" rel="noopener noreferrer"&gt;&lt;code&gt;@grafbase/apollo-link&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.npmjs.com/package/@grafbase/urql-exchange" rel="noopener noreferrer"&gt;&lt;code&gt;@grafbase/urql-exchange&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;  &lt;iframe src="https://www.youtube.com/embed/EaMt6ch80WI" width="710" height="399"&gt;
  &lt;/iframe&gt;
&lt;/p&gt;

&lt;p&gt;  &lt;iframe src="https://www.youtube.com/embed/N2dCu02SJoE" width="710" height="399"&gt;
  &lt;/iframe&gt;
&lt;/p&gt;

&lt;p&gt;Developers not using either of those libraries can still use Live Queries with the native &lt;a href="https://grafbase.com/docs/realtime/live-queries#eventsource" rel="noopener noreferrer"&gt;&lt;code&gt;EventSource&lt;/code&gt;&lt;/a&gt; API.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try It Now!
&lt;/h2&gt;

&lt;p&gt;You can try Live Queries by building your own backend in one simple command:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npx grafbase init
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Once you've modelled your data using the &lt;a href="https://grafbase.com/docs/schema/overview" rel="noopener noreferrer"&gt;schema&lt;/a&gt; you can run your backend locally to build:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npx grafbase dev
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



</description>
      <category>graphql</category>
      <category>webdev</category>
      <category>realtime</category>
      <category>database</category>
    </item>
    <item>
      <title>This Week @ Grafbase - Dec 9</title>
      <dc:creator>Jamie Barton</dc:creator>
      <pubDate>Fri, 09 Dec 2022 13:18:26 +0000</pubDate>
      <link>https://dev.to/grafbase/this-week-grafbase-dec-9-54jc</link>
      <guid>https://dev.to/grafbase/this-week-grafbase-dec-9-54jc</guid>
      <description>&lt;p&gt;Happy Friday 🥳&lt;/p&gt;

&lt;p&gt;It’s been a few weeks since our last update about what’s going on at &lt;a href="https://grafbase.com" rel="noopener noreferrer"&gt;Grafbase&lt;/a&gt;, and for good reason...&lt;/p&gt;

&lt;h2&gt;
  
  
  What’s new?
&lt;/h2&gt;

&lt;p&gt;🎮 &lt;strong&gt;Dashboard tweaks&lt;/strong&gt;&lt;br&gt;
We’ve made some significant changes to our Dashboard UI. You should start to see updates rolling out every few days.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Finbsoafrs23samluwu2h.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Finbsoafrs23samluwu2h.png" alt="Grafbase Project Card" width="800" height="463"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;🛠️ &lt;strong&gt;Bulk Environment Variables&lt;/strong&gt;&lt;br&gt;
We've made it even easier to add environment variables. Check it out! &lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fyhunzrry29kxno1wb1b8.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fyhunzrry29kxno1wb1b8.png" alt="Environment variables UI" width="800" height="320"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;🛰️ &lt;strong&gt;GraphQL Galaxy&lt;/strong&gt;&lt;br&gt;
Grafbase Founder &amp;amp; CEO Fredrik Björk spoke at GraphQL Galaxy with other industry experts on the future of server-side GraphQL.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fe00q64jri43lk50c3nam.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fe00q64jri43lk50c3nam.jpeg" alt="GraphQL Galaxy Panel" width="800" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;📢 &lt;strong&gt;Base64 cursors&lt;/strong&gt;&lt;br&gt;
Collection queries returning edges will now return a base64 encoded &lt;code&gt;cursor&lt;/code&gt; value you can use with the &lt;code&gt;before&lt;/code&gt;/&lt;code&gt;after&lt;/code&gt; pagination arguments. &lt;a href="https://grafbase.com/docs/reference/pagination" rel="noopener noreferrer"&gt;Learn more about pagination&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;🧰 &lt;strong&gt;New home for examples&lt;/strong&gt;&lt;br&gt;
There's a &lt;a href="https://github.com/grafbase/examples/" rel="noopener noreferrer"&gt;new GitHub repo&lt;/a&gt; for all examples! Go check it out.&lt;/p&gt;

&lt;h2&gt;
  
  
  What’s next?
&lt;/h2&gt;

&lt;p&gt;⚡️ &lt;strong&gt;Live Queries&lt;/strong&gt;&lt;br&gt;
We’re putting the final touches on our realtime GraphQL support. Next week we will introduce this officially. For those keen enough, you can try it out today if you dig around the documentation 😉.&lt;/p&gt;

&lt;p&gt;🔢 &lt;strong&gt;Improved numeric operations&lt;/strong&gt;&lt;br&gt;
We’ve made it easier to increment and decrement numeric fields. This change is live in production now but coming to CLI support next week with an official changelog.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;GraphQL Galaxy Workshop&lt;/strong&gt;&lt;br&gt;
In this workshop, we'll cover the basics of GraphQL, and then use that knowledge to build a backend using SDL. Once we've created our schema, we'll run it locally, deploy to production, and create deployment branches for any changes to our schema. We'll finish the workshop by fetching data from our backend from the frontend, as well as adding authentication to lock down data access!&lt;br&gt;
&lt;a href="https://graphqlgalaxy.com/workshops-3h" rel="noopener noreferrer"&gt;https://graphqlgalaxy.com/workshops-3h&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Next week we will introduce some significant changes, including Live Queries, Numeric operations, Improved Documentation, and lots more!&lt;/p&gt;




&lt;p&gt;We love to hear from our users what we can be doing better. No matter how small you might think it is, we want to hear from you!&lt;/p&gt;

&lt;p&gt;Make sure to click &lt;strong&gt;Feedback&lt;/strong&gt; once logged in and share your thoughts. &lt;strong&gt;We read them all!&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fy02jeblz7znfkvm3qx81.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fy02jeblz7znfkvm3qx81.png" alt="Feedback form" width="800" height="474"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Have a great weekend! 💚&lt;/p&gt;

</description>
      <category>graphql</category>
      <category>webdev</category>
      <category>javascript</category>
      <category>api</category>
    </item>
    <item>
      <title>This Week @ Grafbase - Nov 25</title>
      <dc:creator>Jamie Barton</dc:creator>
      <pubDate>Fri, 25 Nov 2022 10:51:57 +0000</pubDate>
      <link>https://dev.to/grafbase/this-week-grafbase-nov-25-149i</link>
      <guid>https://dev.to/grafbase/this-week-grafbase-nov-25-149i</guid>
      <description>&lt;p&gt;Happy Friday 🥳&lt;/p&gt;

&lt;p&gt;These posts provide a summary of everything we've been working on this week at Grafbase.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What's new?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;🔑 &lt;strong&gt;JWT Provider&lt;/strong&gt;&lt;br&gt;
Today we announced the release of a new auth provider strategy that lets you set a &lt;code&gt;secret&lt;/code&gt; to verify JWTs as part of your authorisation strategy.&lt;br&gt;
&lt;a href="https://grafbase.com/changelog/jwt-authorization-provider-added" rel="noopener noreferrer"&gt;https://grafbase.com/changelog/jwt-authorization-provider-added&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fwfxky5va3lmdcs8s8s08.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fwfxky5va3lmdcs8s8s08.png" alt="JWT Provider" width="800" height="420"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;⚒️ &lt;strong&gt;New examples!&lt;/strong&gt;&lt;br&gt;
We've 3 new examples - &lt;a href="https://github.com/grafbase/grafbase/tree/main/examples/fresh" rel="noopener noreferrer"&gt;Fresh&lt;/a&gt;, &lt;a href="https://github.com/grafbase/grafbase/tree/main/examples/solid-start" rel="noopener noreferrer"&gt;SolidStart&lt;/a&gt;, and &lt;a href="https://github.com/grafbase/grafbase/tree/main/examples/nextauthjs-credentials" rel="noopener noreferrer"&gt;NextAuth.js Credentials&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;📚 &lt;strong&gt;New guides!&lt;/strong&gt;&lt;br&gt;
We have got some new guides! &lt;a href="https://grafbase.com/guides/working-with-typescript-and-apollo-client" rel="noopener noreferrer"&gt;Working with TypeScript, React, and Apollo Client&lt;/a&gt;, &lt;a href="https://grafbase.com/guides/username-and-password-authentication-with-next-auth" rel="noopener noreferrer"&gt;Username and Password authentication with NextAuth.js&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;💚 &lt;strong&gt;NuxtNation&lt;/strong&gt;&lt;br&gt;
The NuxtNation conference was last week and you can replay &lt;br&gt;
&lt;a href="https://vi.to/hubs/nuxtnation" rel="noopener noreferrer"&gt;https://vi.to/hubs/nuxtnation&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;We also have a small competition for those who joined NuxtNation. So make sure to checkout the swag link in the email if you attended.&lt;/p&gt;

&lt;p&gt;🔥 &lt;strong&gt;Cloudflare&lt;/strong&gt;&lt;br&gt;
We’re excited to continue building Grafbase for scale with Workers by joining the Cloudflare Workers Launchpad!&lt;br&gt;
&lt;a href="https://blog.cloudflare.com/launchpad-fall-22/" rel="noopener noreferrer"&gt;https://blog.cloudflare.com/launchpad-fall-22/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F3hqzxwtburvk74wz9ui4.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F3hqzxwtburvk74wz9ui4.png" alt="Cloudflare Workers Launchpad cohort" width="800" height="347"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What's next?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;⚡️ &lt;strong&gt;Live Queries&lt;/strong&gt;&lt;br&gt;
General availability for Live Queries is coming very soon! If you'd like early access, please let us know.&lt;/p&gt;

&lt;p&gt;🏎️ &lt;strong&gt;Performance&lt;/strong&gt;&lt;br&gt;
We're working on improving the already fast deployment, and API response times.&lt;/p&gt;

&lt;p&gt;🎮 &lt;strong&gt;Dashboard Updates&lt;/strong&gt;&lt;br&gt;
You should start to see some improvements to the Dashboard soon.&lt;/p&gt;

&lt;p&gt;Stay tuned 👀&lt;/p&gt;

&lt;p&gt;Have a great weekend! 👋&lt;/p&gt;

</description>
      <category>graphql</category>
      <category>webdev</category>
      <category>javascript</category>
      <category>api</category>
    </item>
    <item>
      <title>This Week @ Grafbase - Nov 11</title>
      <dc:creator>Jamie Barton</dc:creator>
      <pubDate>Fri, 11 Nov 2022 16:54:07 +0000</pubDate>
      <link>https://dev.to/grafbase/this-week-grafbase-nov-11-45h6</link>
      <guid>https://dev.to/grafbase/this-week-grafbase-nov-11-45h6</guid>
      <description>&lt;p&gt;Happy Friday 🥳&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;This Week @ Grafbase&lt;/strong&gt; has been all about product, conferences, and realtime!&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What's new?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fdhwd23qvuvq4d1q9tqvx.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fdhwd23qvuvq4d1q9tqvx.png" alt="Grafbase.com" width="800" height="402"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;💅 &lt;strong&gt;New homepage!!&lt;/strong&gt;&lt;br&gt;
We wanted to share with everyone what we're building. The homepage shares more about we've created already as well as what's coming next. Check it out and let us know of any feedback.&lt;br&gt;
&lt;a href="https://grafbase.com" rel="noopener noreferrer"&gt;https://grafbase.com&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;📆 &lt;strong&gt;Date scalar added&lt;/strong&gt;&lt;br&gt;
You can now use the &lt;code&gt;Date&lt;/code&gt; scalar for fields in your models.&lt;br&gt;
&lt;a href="https://grafbase.com/changelog/date-scalar-added" rel="noopener noreferrer"&gt;https://grafbase.com/changelog/date-scalar-added&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;🔢 &lt;strong&gt;&lt;code&gt;@length&lt;/code&gt; directive added&lt;/strong&gt;&lt;br&gt;
You can now set min and max values for the length of a field value or list.&lt;br&gt;
&lt;a href="https://grafbase.com/changelog/length-directive-added" rel="noopener noreferrer"&gt;https://grafbase.com/changelog/length-directive-added&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;🔐 &lt;strong&gt;Model-level authorization rules&lt;/strong&gt;&lt;br&gt;
You can now override the global &lt;code&gt;@auth&lt;/code&gt; rules for each &lt;code&gt;@model&lt;/code&gt; in your schema.&lt;br&gt;
&lt;a href="https://grafbase.com/docs/reference/directives#model-level-authorization-rules" rel="noopener noreferrer"&gt;https://grafbase.com/docs/reference/directives#model-level-authorization-rules&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;🗝️ &lt;strong&gt;Auth groups claim configuration&lt;/strong&gt;&lt;br&gt;
You can now set the &lt;code&gt;groupsClaim&lt;/code&gt; for group-based auth to use a custom claim different from the default groups claim.&lt;br&gt;
&lt;a href="https://grafbase.com/docs/reference/directives#operations" rel="noopener noreferrer"&gt;https://grafbase.com/docs/reference/directives#operations&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;🌉 &lt;strong&gt;Jamstack Conf&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;This week was all about Jamstack Conf! It was a blast to meet the community and see people IRL once again!&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fq0lzahet9qcpdhboyl3v.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fq0lzahet9qcpdhboyl3v.jpeg" alt="Jamie and Colby" width="800" height="1067"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Be sure to check &lt;a href="https://jamstack.org/conf/" rel="noopener noreferrer"&gt;jamstack.org/conf&lt;/a&gt; to watch all of the the talks when they're published!&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What’s next?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;💚 NuxtNation is happening!&lt;br&gt;
This event happens November 16 &amp;amp; 17, online!&lt;br&gt;
&lt;a href="https://nuxtnation.com/" rel="noopener noreferrer"&gt;https://nuxtnation.com&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;💗 We’re close to releasing the initial version of &lt;code&gt;@live&lt;/code&gt; queries! We should have something to show you very, very soon!&lt;br&gt;
&lt;a href="https://grafbase.com/changelog" rel="noopener noreferrer"&gt;Subscribe to the changelog&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;More exciting updates coming next week!&lt;/p&gt;

&lt;p&gt;Have a great weekend 👋&lt;/p&gt;

</description>
      <category>graphql</category>
      <category>webdev</category>
      <category>news</category>
      <category>javascript</category>
    </item>
    <item>
      <title>This Week @ Grafbase - Nov 4</title>
      <dc:creator>Jamie Barton</dc:creator>
      <pubDate>Fri, 04 Nov 2022 10:10:00 +0000</pubDate>
      <link>https://dev.to/grafbase/this-week-grafbase-1nkp</link>
      <guid>https://dev.to/grafbase/this-week-grafbase-1nkp</guid>
      <description>&lt;p&gt;Happy Friday 🥳&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;This Week @ Grafbase&lt;/strong&gt; has been all about product and documentation!&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What's new?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;🛠️ &lt;strong&gt;Docs Quickstart&lt;/strong&gt;&lt;br&gt;
There is now a Quickstart that you can follow to get up to speed with Grafbase in a few short steps.&lt;br&gt;
&lt;a href="https://grafbase.com/docs/quickstart/get-started"&gt;https://grafbase.com/docs/quickstart/get-started&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;🔍 &lt;strong&gt;Update and Delete by unique fields&lt;/strong&gt;&lt;br&gt;
You can now update and delete data by &lt;code&gt;id&lt;/code&gt; and any &lt;code&gt;@unique&lt;/code&gt; field.&lt;br&gt;
&lt;a href="https://grafbase.com/changelog/update-and-delete-by-unique"&gt;https://grafbase.com/changelog/update-and-delete-by-unique&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;iframe width="710" height="399" src="https://www.youtube.com/embed/laY8fQUTVi4"&gt;
&lt;/iframe&gt;
&lt;/p&gt;

&lt;p&gt;▲ &lt;strong&gt;Next.js conf&lt;/strong&gt;&lt;br&gt;
We recently sponsored Next.js conf and have a free workshop you can join happening later this month — &lt;a href="https://docs.google.com/forms/d/e/1FAIpQLScv01U8yk8H_xYfc12IF8fiOt9hFcaQmI2kaqIAa_eSEowzHw/viewform"&gt;more info&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;📈 &lt;strong&gt;Funding announcement&lt;/strong&gt;&lt;br&gt;
You may have already seen but we announced a $7.3m raise to build the data platform of the future.&lt;br&gt;
&lt;a href="https://grafbase.com/blog/announcing-7-3m-funding"&gt;https://grafbase.com/blog/announcing-7-3m-funding&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What's next?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;🫐 We're attending and sponsoring &lt;a href="https://jamstack.org/conf/"&gt;Jamstack Conf&lt;/a&gt;. There's still tickets available for any last minute attendees. Get 40% off your ticket with code: &lt;code&gt;GRAFBASE40&lt;/code&gt;.&lt;br&gt;
&lt;a href="https://jamstack.org/conf"&gt;https://jamstack.org/conf&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;💚 We're also sponsoring Nuxt Nation! This event happens November 16 &amp;amp; 17, online!&lt;br&gt;
&lt;a href="https://nuxtnation.com/"&gt;https://nuxtnation.com&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;🔓 We're working on more Data Validation topics and investigating how to properly implement migrations, resolvers, and more. &lt;a href="https://discord.gg/grafbase"&gt;Join the community on Discord&lt;/a&gt; to have your say on how we should build the data platform for the future!&lt;/p&gt;

&lt;p&gt;More exciting updates coming next week!&lt;/p&gt;

&lt;p&gt;Have a great weekend 👋&lt;/p&gt;

</description>
      <category>grafbase</category>
      <category>graphql</category>
      <category>news</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
