Jan

Seems like eloqnt/cli is helpful to you! Anything it could do that it doesn't today?

next-intl 4.14 is out with 𝚞𝚜𝚎𝙴𝚡𝚝𝚛𝚊𝚌𝚝𝚎𝚍 improvements! → Switch 𝚖𝚜𝚐𝚒𝚍 of .𝚙𝚘 codec to source string → Support 𝙿𝚛𝚘𝚖𝚒𝚜𝚎.𝚊𝚕𝚕 with 𝚐𝚎𝚝𝙴𝚡𝚝𝚛𝚊𝚌𝚝𝚎𝚍 → Update 𝚜𝚠𝚌_𝚌𝚘𝚛𝚎 to 77

With 𝚗𝚎𝚡𝚝/𝚛𝚘𝚘𝚝-𝚙𝚊𝚛𝚊𝚖𝚜, you can cache more of your app. If you read a locale from 𝚌𝚘𝚘𝚔𝚒𝚎𝚜() or 𝚑𝚎𝚊𝚍𝚎𝚛𝚜(), this is request data. A locale from [𝚕𝚘𝚌𝚊𝚕𝚎] is a cache key. Your routing strategy becomes a caching decision.

Next.js 16.3 includes better ISR: Pages can now show an instant loading shell on first visit, and then upgrade to a fully prerendered page in the background (cached). This comes in handy for apps with a large number of locales!

Next.js 16.3 is out with next/root-params 🥹🥹🥹 I've literally waited years for this! Use it today with next-intl 🔗↓

With the number of lint rules for eloqnt/cli growing continuously, I've now added dedicated pages for each one. Is this helpful? Anything to add/change?

eloqnt/studio now has built-in Crowdin synchronization

MDX components in eloqnt/studio now render twice: → React for humans → Markdown for agents

TIL in monorepos you can split 𝙲𝙻𝙰𝚄𝙳𝙴.𝚖𝚍 files by package, much tidier 💡 𝚎𝚕𝚘𝚚𝚗𝚝/ ─ 𝙲𝙻𝙰𝚄𝙳𝙴.𝚖𝚍 ─ 𝚊𝚙𝚙𝚜/ ─ 𝚜𝚝𝚞𝚍𝚒𝚘-𝚠𝚎𝚋/𝙲𝙻𝙰𝚄𝙳𝙴.𝚖𝚍 ─ 𝚙𝚊𝚌𝚔𝚊𝚐𝚎𝚜/ ─ 𝚌𝚕𝚒/𝙲𝙻𝙰𝚄𝙳𝙴.𝚖𝚍 ─ 𝚜𝚍𝚔/𝙲𝙻𝙰𝚄𝙳𝙴.𝚖𝚍

Shipped a much-needed docs revamp for eloqnt/studio. → Zero-to-lint quickstart (with a prompt) → Copyable .𝚖𝚍 links → Support for 𝙰𝚌𝚌𝚎𝚙𝚝: 𝚝𝚎𝚡𝚝/𝚖𝚊𝚛𝚔𝚍𝚘𝚠𝚗 → Split into multiple pages → Public changelogs → It looks just a lot nicer :D

When should you translate your app? After every change? Before a commit, after a commit? What about the moment you switch the PR from "draft" to "ready for review"? bsky.app/profile/aman...

Today, I'm launching eloqnt/studio. An AI-based toolchain that helps you ship high-quality translations. All from the command line. 𝚎𝚕𝚘𝚚𝚗𝚝 𝚕𝚒𝚗𝚝 𝚎𝚕𝚘𝚚𝚗𝚝 𝚛𝚎𝚟𝚒𝚎𝚠 𝚎𝚕𝚘𝚚𝚗𝚝 𝚝𝚛𝚊𝚗𝚜𝚕𝚊𝚝𝚎 With our hosted model, or bring your own. 🔗↓

Start linting your strings today. 𝚗𝚙𝚖 𝚒 @𝚎𝚕𝚘𝚚𝚗𝚝/𝚌𝚕𝚒 --𝚜𝚊𝚟𝚎-𝚍𝚎𝚟 Add .𝚎𝚕𝚘𝚚𝚗𝚝/𝚌𝚘𝚗𝚏𝚒𝚐.𝚝𝚜 and run: 𝚗𝚙𝚡 𝚎𝚕𝚘𝚚𝚗𝚝 𝚕𝚒𝚗𝚝 Docs → studio.eloqnt.dev/docs

Today, I'm launching eloqnt/studio. An AI-based toolchain that helps you ship high-quality translations. All from the command line. 𝚎𝚕𝚘𝚚𝚗𝚝 𝚕𝚒𝚗𝚝 𝚎𝚕𝚘𝚚𝚗𝚝 𝚛𝚎𝚟𝚒𝚎𝚠 𝚎𝚕𝚘𝚚𝚗𝚝 𝚝𝚛𝚊𝚗𝚜𝚕𝚊𝚝𝚎 With our hosted model, or bring your own. 🔗↓

The backbone of eloqnt/studio is its AI engine. You can either use a hosted version, or bring your own model—anything supported by the AI SDK. This also includes 3rd-party plugins for using your Claude Code or Codex sub (subject to their latest terms).

Today, I'm launching eloqnt/studio. An AI-based toolchain that helps you ship high-quality translations. All from the command line. 𝚎𝚕𝚘𝚚𝚗𝚝 𝚕𝚒𝚗𝚝 𝚎𝚕𝚘𝚚𝚗𝚝 𝚛𝚎𝚟𝚒𝚎𝚠 𝚎𝚕𝚘𝚚𝚗𝚝 𝚝𝚛𝚊𝚗𝚜𝚕𝚊𝚝𝚎 With our hosted model, or bring your own. 🔗↓

What makes your product or service unique? Terms to keep, tone to hold, a glossary—all placed in simple markdown styleguides. Easy to set up and maintain, and the format your agent already speaks. It's AGENTS.md, but for translations.

Today, I'm launching eloqnt/studio. An AI-based toolchain that helps you ship high-quality translations. All from the command line. 𝚎𝚕𝚘𝚚𝚗𝚝 𝚕𝚒𝚗𝚝 𝚎𝚕𝚘𝚚𝚗𝚝 𝚛𝚎𝚟𝚒𝚎𝚠 𝚎𝚕𝚘𝚚𝚗𝚝 𝚝𝚛𝚊𝚗𝚜𝚕𝚊𝚝𝚎 With our hosted model, or bring your own. 🔗↓

So eloqnt/studio is different. It's not a model, but a pipeline. Every string moves through well-defined steps: ① Static analysis ② Source text review ③ Context enrichment ④ Translate

Today, I'm launching eloqnt/studio. An AI-based toolchain that helps you ship high-quality translations. All from the command line. 𝚎𝚕𝚘𝚚𝚗𝚝 𝚕𝚒𝚗𝚝 𝚎𝚕𝚘𝚚𝚗𝚝 𝚛𝚎𝚟𝚒𝚎𝚠 𝚎𝚕𝚘𝚚𝚗𝚝 𝚝𝚛𝚊𝚗𝚜𝚕𝚊𝚝𝚎 With our hosted model, or bring your own. 🔗↓

Get early access → studio.eloqnt.dev Small batches rolling out soon. Full story below 🧵

I've been pretty quiet lately since I've been secretly working on a new project ❤️