Update npmx tagline translation

[shuuji3]

This is a tracking issue to update the npmx tagline for each language.

We updated the tagline from "a better browser for the npm registry" to "a fast, modern browser for the npm registry" on Feb 6. We want to make a good npm browser, but we don't want to say that we are replacing npmjs.com or that it is not as good. "Better" might be misunderstood by some npmx users, so we chose "fast, modern" to better describe our intent.

We also need to update seo.home.description along with the tagline. These two are the minimum. If you have time, it would be great if you could update new strings as well.

The alpha release is on March 3rd. We hope to have the updates by then. I tagged those who translated the tagline before the update (the date is when the tagline was last updated). Thank you!

• 2026-01-27 fr-FR.json @jycouet fix(i18n): update French translations for tagline, add all missing keys #1701
• 2026-01-27 it-IT.json @MatteoGabriele feat(i18n): tagline and seo update italian #1691
• 2026-01-28 zh-CN.json @9romise feat(i18n): update zh-CN translations #1733
• 2026-01-30 ar.json @skaldebane
• 2026-01-30 es.json @userquin feat(i18n): change npmx tagline and add missing Spanish translations #1703
• 2026-01-30 ru-RU.json @dragomano fix(i18n): update Russian translations #1693
• 2026-01-31 az-AZ.json @chz feat(i18n): update az-AZ tagline and sync translations #1692
• 2026-01-30 uk-UA.json @thevrus feat(i18n): update UA translations: add missing keys, change tagline #1722
• 2026-01-31 pl-PL.json @wojtekmaj feat(i18n): update Polish translations #1716
• 2026-01-31 hu-HU.json @THE-SIMPLE-MARK
• 2026-01-31 pt-BR.json @brenoepics
• 2026-02-01 ne-NP.json @whoisanku
• 2026-02-01 id-ID.json @narr07 feat(i18n): update Indonesian translation #1709
• 2026-02-01 cs-CZ.json @VentyCZ fix(i18n): update Czech translations #1719
• 2026-02-02 hi-IN.json @trivikr
• 2026-02-03 mr-IN.json @trivikr
• 2026-02-05 zh-TW.json @serkodev
• 2026-02-06 en.json @shuuji3
• 2026-02-06 nb-NO.json @bonsak
• 2026-02-07 te-IN.json @KirankumarAmbati
• 2026-02-08 ja-JP.json @shuuji3
• 2026-02-09 bn-IN.json @kunalk16
• 2026-02-13 bg-BG.json @radosvet93
• 2026-02-23 ta-IN.json @Meganathanrbm
• 2026-02-27 kn-IN.json @harshith-venkatesh
• 2026-02-26 de-DE.json @trueberryless

[userquin]

@shuuji3 for Spanish #1696

[wojtekmaj]

Is there a way to reset translations that were updated in source language since the last time they were written? That would be immensely helpful when maintaining translations.

[VentyCZ]

Is there a way to reset translations that were updated in source language since the last time they were written? That would be immensely helpful when maintaining translations.

I guess it would be possible to git blame the two files, but it would not be very reliable. I'd really like the translation files to have the source string there, so I don't have to look into the en file as reference. It would be really helpful in this case too as we'd just detect diff between the original string in both files.

How does that sound? This is the only downside (AFAIK) of using translation keys instead of using base texts (ie. in english)

PS: I'll raise this in the i18n Discord later

[wojtekmaj]

Mistakenly closed via #1692

[userquin]

Mistakenly closed via #1692

I think not being closed by #1692, Daniel closed this before PR merged...