Skip to content

Announce Bun and Deno build runtimes for Sites#3006

Open
atharvadeosthale wants to merge 3 commits into
mainfrom
bun-deno-runtimes
Open

Announce Bun and Deno build runtimes for Sites#3006
atharvadeosthale wants to merge 3 commits into
mainfrom
bun-deno-runtimes

Conversation

@atharvadeosthale
Copy link
Copy Markdown
Member

Blog post and changelog entry announcing Bun (1.0-1.3) and Deno (1.40-2.6) as build runtimes for Appwrite Sites.

@appwrite
Copy link
Copy Markdown

appwrite Bot commented May 18, 2026

Appwrite Website

Project ID: 69d7efb00023389e8d27

Sites (1)
Site Status Logs Preview QR
 website
69d7f2670014e24571ca
Building Building View Logs Preview URL QR Code

Website (appwrite/website)

Project ID: 684969cb000a2f6c0a02

Sites (1)
Site Status Logs Preview QR
 website
68496a17000f03d62013
Queued Queued View Logs Preview URL QR Code


Tip

Preview deployments create instant URLs for every branch and commit

@greptile-apps
Copy link
Copy Markdown
Contributor

greptile-apps Bot commented May 18, 2026

Greptile Summary

This PR adds a blog post and changelog entry announcing Bun (1.0–1.3) and Deno (1.40–2.6) as build runtimes for Appwrite Sites.

  • The blog post (+page.markdoc) is complete with valid frontmatter, correct .avif image references, and an existing atharva author record.
  • The changelog entry version lists match the blog post exactly, and the arrow_link points to the correct announcement URL.
  • The two .avif images are present in static/images/blog/announcing-bun-deno-runtimes/, and the .optimize-cache.json entries (with .png keys) are the normal output of the optimize-assets.js script after converting the originals.

Confidence Score: 5/5

Content-only PR adding a blog post, changelog entry, and two static images — no logic changes, no data mutations.

All changed files are static content. Image paths in the markdoc files match the actual .avif files on disk, the author key resolves to an existing author page, and the changelog/blog version lists are consistent with each other.

No files require special attention.

Important Files Changed

Filename Overview
src/routes/blog/post/announcing-bun-deno-runtimes/+page.markdoc New blog post announcing Bun/Deno build runtimes; author reference valid, image paths match actual .avif files, frontmatter fields look correct.
src/routes/changelog/(entries)/2026-05-19.markdoc New changelog entry; version lists match the blog post, cover image path is correct, arrow_link points to the announcement post.
.optimize-cache.json Two .png cache entries added for the new images; these are the expected historical keys written by optimize-assets.js after converting the originals to .avif — not a mismatch.

Reviews (3): Last reviewed commit: "Address review: rebold lead, drop out-of..." | Re-trigger Greptile

callToAction: true
---

Today, we are happy to announce that **Bun and Deno are now available as build runtimes for Appwrite Sites, and they work out of the box with zero configuration**. You can pick any supported version, from **Bun 1.0** up to the latest **Bun 1.3**, and from **Deno 1.40** up to the latest **Deno 2.6**, in the Console build runtime dropdown for any Node-based framework, and your existing site will build without any changes to your project, your `package.json`, or your build command.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Today, we are happy to announce that **Bun and Deno are now available as build runtimes for Appwrite Sites, and they work out of the box with zero configuration**. You can pick any supported version, from **Bun 1.0** up to the latest **Bun 1.3**, and from **Deno 1.40** up to the latest **Deno 2.6**, in the Console build runtime dropdown for any Node-based framework, and your existing site will build without any changes to your project, your `package.json`, or your build command.
Today, we are happy to announce that **Bun and Deno are now available as build runtimes for Appwrite Sites**, and they work out of the box with zero configuration. You can pick any supported version, from **Bun 1.0** up to the latest **Bun 1.3**, and from **Deno 1.40** up to the latest **Deno 2.6**, in the Console build runtime dropdown for any Node-based framework, and your existing site will build without any changes to your project, your `package.json`, or your build command.

Also, how true is zero configuration? It might cause a little bit of confusion. I'd rather not have it there and just show the simplicity in the steps later


# Available versions

The build runtime dropdown for Node-based Sites frameworks now includes:
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We also need to update the self-hosting docs for Sites to include the runtime versions

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure if self-hosted supports this yet 🤔
My changes only affect cloud for now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants