fix: update about page description

[vladh]

🔗 Linked issue

N/A

🧭 Context

The current description is:

npmx is a better UX/DX for the npm package registry and tooling.

I don't think this makes sense, for two reasons.

First, “npmx is a better user experience for the npm package registry” implies “npmx is a user experience”. But that doesn't really make sense. npmx is a package browser that provides a better user experience.

Secondly, in “npmx is a better UX for the npm package registry and tooling”, I'm not clear on what the “tooling” is. At best, this would be something like “npmx offers a better UX for the npm tooling”. But what is the npm tooling? I don't think this short description of the basics of npmx needs to get into the weeds about this, though.

📚 Description

I've rewritten this as follows:

npmx is a package browser offering a better UX/DX for the npm package registry.

I think this solves the above problems.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
npmx.dev	Ready	Preview, Comment	Mar 8, 2026 0:13am

2 Skipped Deployments

Project	Deployment	Actions	Updated (UTC)
docs.npmx.dev	Ignored	Preview	Mar 8, 2026 0:13am
npmx-lunaria	Ignored		Mar 8, 2026 0:13am

[github-actions]

Lunaria Status Overview

🌕 This pull request will trigger status changes.

Learn more

By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.

You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

File	Note
i18n/locales/en.json	Source changed, localizations will be marked as outdated.

Warnings reference

Icon	Description
🔄️	The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

📢 Thoughts on this report? Let us know!

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 1048e79e-6aa3-43f6-b2a2-d18be847160d

📥 Commits

Reviewing files that changed from the base of the PR and between 03f7ecd and 219e73a.

📒 Files selected for processing (1)

• i18n/locales/en.json

---

📝 Walkthrough

Walkthrough

A localised string in the English translation file has been updated. The description text for "what_we_are" has been revised to describe npmx as "a package browser offering a {betterUxDx} for the npm package registry" instead of the previous phrasing that referenced both the registry and tooling. The change replaces one line of text with an alternative version that adjusts the primary focus of the description.

Suggested reviewers

• danielroe
• graphieros

🚥 Pre-merge checks | ✅ 1

✅ Passed checks (1 passed)

Check name	Status	Explanation
Description check	✅ Passed	The pull request description clearly explains the rationale for updating the About page description, identifying specific grammatical and clarity issues with the original wording and providing a well-reasoned alternative.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

Tip

Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs).
Share your feedback on Discord.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[alexdln]

I agree that the current wording doesn't capture who npmx is, but the update limiting us a bit more. We have a full-fledged admin panel for managing packages, as well as likes and profile

One more issue here is that the wording through betterUxDx is also outdated and is no longer correct to us

[vladh]

I agree that the current wording doesn't capture who npmx is, but the update limiting us a bit more. We have a full-fledged admin panel for managing packages, as well as likes and profile

Okay! I see you marked this as “requested changes” but I don't see any specific changes being requested. So I'll just leave this open for discussion among the community.