Gary Stupak

Shipping code at the Edge. Cloudflare & Astro enthusiast. Building EdgeKits.

[Gary Stupak @GaryEdgeKits]

Every Astro i18n library you can install today hits the same four walls. I tried five before realizing I needed a different shape entirely.

Wrote it up - 7 maturity levels, my honest take on every library, the edge-native pattern at the end.

https://t.co/24Auataxj5

[Gary Stupak @GaryEdgeKits]

Updated my Astro i18n guide - Intlayer was missing, and it deserved a place. Now co-default with Paraglide for 2026. https://t.co/24Auataxj5

[Gary Stupak @GaryEdgeKits]

@hridoyreh You should control every paragraph of your or "your" content.

[Gary Stupak @GaryEdgeKits]

@aymericzip Thanks Aymeric - appreciated, especially coming from someone shipping Intlayer. Different routes through the same problem. Both stories are useful in the ecosystem. Happy to compare notes anytime.

[Gary Stupak @GaryEdgeKits]

Every Astro i18n library you can install today hits the same four walls. I tried five before realizing I needed a different shape entirely.

Wrote it up - 7 maturity levels, my honest take on every library, the edge-native pattern at the end.

https://t.co/24Auataxj5

[Gary Stupak @GaryEdgeKits]

The pattern is clear. The next word isn't.
Drop your guess.

P.S. Are you sure it's about poetry? 😉

[Gary Stupak @GaryEdgeKits]

Old habits die hard. Coming from traditional i18n libs, I instinctively kept my locales JSONs inside the src directory in the astro-edgekits-core.

But with an Edge-native architecture where translations (data) and logic (code) are strictly separated, there's zero need for that. They never hit the client bundle anyway, but moving them to the project root makes the architecture much cleaner.

Will update the repo soon! 🚀 #i18n #astrobuild #Cloudflare #webdev

[Ashley Peacock @_ashleypeacock]

I built FlareCalc, the ultimate Cloudflare cost calculator to help you estimate spend 💸

There is no Cloudflare cost calculator I can find that covers the entire developer platform, and the ones out there are just for Workers and use outdated pricing

[Gary Stupak @GaryEdgeKits]

@_ashleypeacock Awesome work, congratulations! The ecosystem definitely needed an up-to-date calculator for the whole dev platform. Bookmarked!

[Gary Stupak @GaryEdgeKits]

You can find the full March digest with a lot of other great updates here: https://t.co/PkSO1RKwrt

[Gary Stupak @GaryEdgeKits]

Incredibly honored to see my article featured in the official @astrodotbuild monthly digest! 🚀

I spent a lot of time figuring out how to stop shipping heavy i18n JavaScript to the client. The solution? Moving the entire localization logic to the Edge using Astro and Cloudflare Workers.

Turns out, Edge-native i18n is the way to go. Huge thanks to the Astro team for the shoutout! 🙌

You can check out the full guide here:
https://t.co/84O1AJ9bOG
https://t.co/asvDAo8x5O

#webdev #astrobuild #cloudflare #webperf

[Gary Stupak @GaryEdgeKits]

The biggest trap in client-side localization? Form validation. 🛑

If you use react-hook-form + zod, translating errors usually means shipping massive JSON dictionaries directly to the browser. Your React bundle bloats, TBT spikes, and Web Vitals tank.

Here’s how we fix it in Part 2 of the Edge-Native i18n guide 👇

[Gary Stupak @GaryEdgeKits]

I wrote a massive deep-dive on how to build this exact architecture.

If you want to master Zero-JS React localization and Astro Actions, check out the full post!

Would love to hear your feedback! 🤝

📖 Article: https://t.co/RfSSaZiNz4

#AstroJS #CloudflareWorkers #ReactJS #WebPerf

[Gary Stupak @GaryEdgeKits]

The biggest trap in client-side localization? Form validation. 🛑

If you use react-hook-form + zod, translating errors usually means shipping massive JSON dictionaries directly to the browser. Your React bundle bloats, TBT spikes, and Web Vitals tank.

Here’s how we fix it in Part 2 of the Edge-Native i18n guide 👇

[Gary Stupak @GaryEdgeKits]

But what about dynamic User-Generated Content (UGC)?

Storing localized data in @CloudflareDev D1 requires the right schema. We skip the "Wide Table" anti-pattern and use JSON columns with @DrizzleORM.

The result? Blazing-fast, single-read queries on the Edge with Zero JOINs. ⚡

[Gary Stupak @GaryEdgeKits]

After trying dozens of tech stacks over the years, I finally found the one I truly fell in love with: @astrodotbuild + @CloudflareDev. 🧡

Huge thanks to @kristianf_ and @craigsdennis - your videos and open-source repos were a massive help on this journey! 🙏

So, finally, I've started my first project with this stack. 🧵👇

[Gary Stupak @GaryEdgeKits]

I wrote a deep-dive article on how to build this architecture and open-sourced the starter template so you don't have to build it from scratch.

Would love to hear any feedback from the community!

📖 Article: https://t.co/84O1AJ9bOG
💻 GitHub: https://t.co/63omGAZmIL

#AstroJS #Cloudflare #WebDev

[Gary Stupak @GaryEdgeKits]

After trying dozens of tech stacks over the years, I finally found the one I truly fell in love with: @astrodotbuild + @CloudflareDev. 🧡

Huge thanks to @kristianf_ and @craigsdennis - your videos and open-source repos were a massive help on this journey! 🙏

So, finally, I've started my first project with this stack. 🧵👇

[Gary Stupak @GaryEdgeKits]

So I moved the logic entirely to the network edge.
⚡️ Astro Middleware handles the routing
⚡️ Cloudflare KV stores the translations
⚡️ Cache API serves them instantly

The result? A true Zero-JS i18n architecture. The browser gets pure, translated HTML.