Messages: find and remove English messages that no component uses

Aperta
  • Qualcosa non va?
#535 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
73/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
github-actions, nextjs, typescript
Ambito
ci-cd, internationalization, performance

Direzione di ricerca

Start with lib/i18n/messages/en.ts, lib/i18n/messages.test.ts, and lib/i18n/dynamic-key.ts; inspect how catalogs and runtime-built keys are represented. Then locate the scripts and CI configuration to add the warning check, and read docs/translating.md for the expected documentation style. Done when pnpm check:messages runs in CI, unused keys are removed from all four catalogs and listed with byte savings in the PR, and the tests pass.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

area: docs difficulty: easy enhancement good first issue help wanted performance v2.0.0

Summary

The English catalog is in every route's first load, so every unused message costs bytes everywhere. A script can list the keys in en.ts that no source file refers to (allowing for keys built from a prefix) so they can be removed from all four catalogs.

Part of the 2.0.0 plan: fewer, better and fully tested studios, on a calmer and faster site.

Where to look

  • lib/i18n/messages/en.ts and lib/i18n/messages.test.ts
  • scripts/ (a place for the check)
  • lib/i18n/dynamic-key.ts (keys built at run time)

Behaviour

  • Write a script that lists keys with no reference and no matching dynamic prefix, and run it in CI as a warning.
  • Remove the unused keys from en, es, fr and hi.
  • Do not remove a key used through a template string: list those prefixes in one place.

Acceptance criteria

  • The script runs with pnpm check:messages and is explained in docs/translating.md.
  • The removed keys are listed in the pull request, with the bytes saved.
  • All tests pass.

Getting started: fork the repo, then pnpm install and pnpm dev (Node 22+, pnpm 11, no API keys). Before opening a PR, run pnpm typecheck && pnpm test && pnpm lint && pnpm format:check && pnpm check:dashes && pnpm build (CI fails on unformatted files, so pnpm format first). See CONTRIBUTING.md and the first contribution walkthrough.

Everything needed is in the repository. This doesn't need maintainer access, secrets or paid services. Comment below to claim it, and ask questions here any time.

Lingua principale
TypeScript
Stelle
11
Fork
3
Merge medio
6h 9m
PR unite (30g)
73

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di yakew7/DesignHub

Tutte le issue di yakew7/DesignHub

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.