docs: npm comparison/features

[danielroe]

this might be too verbose e.g. for the readme, but this is almost more for my own brain to keep track of things.

wdyt?

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
docs.npmx.dev	Ready	Preview, Comment	Feb 12, 2026 6:50am
npmx.dev	Ready	Preview, Comment	Feb 12, 2026 6:50am

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
npmx-lunaria	Ignored		Feb 12, 2026 6:50am

[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]

📝 Walkthrough

Walkthrough

This pull request updates documentation to provide more comprehensive feature coverage and detailed comparisons. The README.md file expands the comparison table with npmjs.com to include granular categorisation of features across package browsing, admin capabilities, and npmx.dev-specific functionality. The features documentation (docs/content/2.guide/1.features.md) is reorganised and significantly expanded with new feature categories, detailed descriptions of package viewing capabilities, security and provenance features, user administration functions, social features, and an extensive keyboard shortcuts reference. The changes restructure existing information into a more detailed and categorised format.

Suggested reviewers

• serhalp
• graphieros

🚥 Pre-merge checks | ✅ 1

✅ Passed checks (1 passed)

Check name	Status	Explanation
Description check	✅ Passed	The description acknowledges the changes are documentation updates related to npm comparison and features, directly referencing the changeset.

_{✏️ 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
• Commit unit tests in branch docs/comparison

---

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

[coderabbitai]

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

docs/content/2.guide/1.features.md (1)

254-266: ⚠️ Potential issue | 🟡 Minor

Align badge colour parameter naming.

You describe color but the examples use colorB, which will confuse readers and lead to broken badges. Please standardise on one parameter name (and update examples accordingly).

🔧 Example alignment (if `color` is correct)

-| **Hot Pink**   | `.../badge/version/nuxt?colorB=ff69b4` |
-| **Pure Black** | `.../badge/version/nuxt?colorB=000000` |
-| **Brand Blue** | `.../badge/version/nuxt?colorB=3b82f6` |
+| **Hot Pink**   | `.../badge/version/nuxt?color=ff69b4`  |
+| **Pure Black** | `.../badge/version/nuxt?color=000000`  |
+| **Brand Blue** | `.../badge/version/nuxt?color=3b82f6`  |

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Hyphenate compound adjective.

“open source projects” should be “open‑source projects” when used as a compound adjective.

✏️ Proposed tweak

-| :icon{name="i-simple-icons-codeberg"} [Codeberg](https://codeberg.org)    | Free hosting for open source projects |
+| :icon{name="i-simple-icons-codeberg"} [Codeberg](https://codeberg.org)    | Free hosting for open‑source projects |

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	| :icon{name="i-simple-icons-codeberg"} [Codeberg](https://codeberg.org) | Free hosting for open source projects |
	| :icon{name="i-simple-icons-codeberg"} [Codeberg](https://codeberg.org) | Free hosting for open-source projects |

🧰 Tools

🪛 LanguageTool

[uncategorized] ~156-~156: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...s://codeberg.org) | Free hosting for open source projects | | :icon{name="i-simple-icons...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

[whitep4nth3r]

What about rendering this on an actual web page on the front end? 🤓