Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Curated package collections grouped by category

未关闭
#2,890 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
30/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
冷清
技术栈
nuxt, typescript
领域
frontend

调研方向

The issue names no files or tests; start by reading how existing package pages are organized and how users navigate between them. Define the scope and curation approach for category collections before implementation; done should let users browse packages by category and compare alternatives, with a path from a package page to its collection.

由索引模型根据 Issue 内容生成。

描述

back e18e front needs discussion social
Describe the feature

It would be great to have curated package collections grouped by category (e.g. "arg parsers", "i18n", "bundlers", "test runners") so users can browse and compare alternatives in the same space without having to search npm blindly.

Use cases:

  • You need an arg parser but don't know what options exist beyond the one you already use
  • You want to compare bundle size, weekly downloads, and maintenance status of similar packages side by side
  • Discovering actively maintained alternatives when a package gets deprecated
  • When you're checking out a package, maybe on the same page there will be a link to the collection of all packages in that category

Alternatives considered:

  • npmtrends.com, npm-compare.com -> great for comparing packages, but do not have curated category lists & pages for each package as npmx already has
  • npm search -> too noisy, no curation
  • Awesome lists on GitHub -> static and hard to compare metrics

Notable examples:

https://npmtrends.com/i18n-vs-i18next
Image

https://npm-compare.com/eventemitter3,mitt,pubsub-js
Image

Additional information
  • Would you be willing to help implement this feature?
Final checks
主要语言
TypeScript
星标
3.6k
派生
533
平均合并
3 天 14 小时
30 天内合并 PR
39

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

npmx-dev/npmx.dev 的其他 Issue

查看 npmx-dev/npmx.dev 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。