X Bookmarks — 2024 KW32: Type-safe i18n for Next.js and document data extraction

August 8, 2024

|bookmarks

by Florian Narr

X Bookmarks — 2024 KW32: Type-safe i18n for Next.js and document data extraction

@pontusab — next-international as the best i18n solution for Next.js

I believe that next-international for @nextjs is the best i18n package:

  • 100% Type-safe
  • Server and Client, Static Rendering
  • No dependencies, lazy-loaded

That's interesting because most i18n libraries for Next.js either skip type safety entirely or bolt it on awkwardly. next-international gives you actual TypeScript completion on translation keys, works with both Server and Client Components, and doesn't drag in a dependency tree to do it. Zero dependencies and lazy loading means you're not paying for strings you don't render.

@prasann_pandya — Myparser: structured data extraction from any document

Introducing Myparser:

The simplest way to extract structured data from documents.

Just upload any document, specify what you want to extract and get a spreadsheet (.csv) with data extracted.

Works with scanned documents and also captures text from images.

Honestly just saved this because document-to-structured-data is a problem that keeps coming up. The pitch is straightforward: upload a PDF or scanned doc, describe the fields you want, get a CSV. If it handles messy real-world scans reliably, that's genuinely useful for anyone automating data entry pipelines. Worth a test run before committing to it.