Pinned
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. 🔗↓
- Mixed routing with 🌐 next-intl → Locale prefixes on public pages → No prefix on pages for logged-in users
- 🌐 next-intl 4.0 beta → Revamped augmented types → Strictly-typed locale → Strictly-typed ICU arguments → GDPR compliance → Modernized build ouput → Preparation for PPR, dynamicIO & rootParams
- 🌐 next-intl v3 → Support for Server Components → New async APIs → Internationalized routing
- Announcing 🌐 learn.next-intl.dev! Have a look and be the first to hear about the launch early next year!
- Replying to @jamannnnnnI was skeptical, but you get productive pretty fast. The weirdest thing to me was providing the initial state to useState in the render function. It's really nice though to extract utilities like useWindowSize, useNodeSize and useScrollToBottom into small composable hooks.
- Thank you so much for the shout-out to next-intl-docs.vercel.app/docs/next-13 in the new Next.js 13 docs @leeerob 🙌 beta.nextjs.org/docs/guides/in…
- Took @framer Motion for a spin and implemented a directional stagger effect in a grid 🙂. The delay is calculated based on the item position and therefore works for responsive layouts. Framer Motion is 👌. @reactjs Demo: q416h.codesandbox.io Code: codesandbox.io/s/framer-motio…
- Replying to @profulsadangiAlways #1 👍 - Clearly separates the function from variable declarations - In case there's a direct return, it's later easier to add a body, also temporarily to add logging - It's more explicit about return values - I'd also assume this syntax is more beginner friendly
- 🌐 next-intl@4 development is in full swing! After a year of feature development, this release mostly aims to tidy up the API surface to ensure the library remains lean—no surprises. One area of improvement is an overhauled API for augmenting types!
