Indicate more prominently when a package has one or several "bin"
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 45/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 冷清
- 技术栈
- nuxt, typescript
调研方向
Start by reading the package page's “Get Started” section and existing badges, then trace how package metadata is used in the search results and filters. The issue names no source files or tests, so locate those entry points in the repository before choosing a scope. Done means packages with one or more binaries are clearly identified, their names or count are surfaced, and the requested search filter is addressed.
由索引模型根据 Issue 内容生成。
描述
Describe the feature
Hello
Currently when a given package can be used as a "binary", like ESLint, the "Get Started" section of the page is expanded to show npx (and related for other package-manager) command in the short snippet. (more info at https://github.com/npmx-dev/npmx.dev/issues/694)
Example with Prettier:
npm install prettier
npm install -D prettier
npx prettier
This is great! But I would argue that it could also be surfaced more prominently as a badge (next to the existing ones like ✓ Types, ✓ ESM…) to be even more discoverable. Because it took me a while to see the aforementioned npx line. My eyes were stubbornly skipping this "Get Started" snippet.
Also, some packages expose more than 1 "bin".
For example this is the case of Ts-node
"bin": {
"ts-node": "dist/bin.js",
"ts-node-cwd": "dist/bin-cwd.js",
"ts-node-esm": "dist/bin-esm.js",
"ts-node-script": "dist/bin-script.js",
"ts-node-transpile-only": "dist/bin-transpile.js",
"ts-script": "dist/bin-script-deprecated.js"
},
So it would be great that this mention of "6 binaries", and even their names be displayed somewhere.
Finally, in the search-engine result list, it would be great to be able to filter by packages which expose "bin".
Thanks
Additional information
- Would you be willing to help implement this feature?
Final checks
- Read the contribution guide.
- Check existing issues.
- 主要语言
- TypeScript
- 星标
- 3.6k
- 派生
- 533
- 平均合并
- 5 天 1 小时
- 30 天内合并 PR
- 36
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
npmx-dev/npmx.dev 的其他 Issue
-
Enable pnpm strictPeerDependencies check可能已有人在做 @cylewaitforit 于 1 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 65/100
维护者通常 1 天内回复
-
a11y front
难度 2/5 1-3 小时 新手友好度 67/100
npmx-dev/npmx.dev#2914 · 3 条评论 ·
维护者通常 1 天内回复
-
front i18n
难度 2/5 1-3 小时 新手友好度 64/100
npmx-dev/npmx.dev#2831 · 1 个 reaction ·
维护者通常 1 天内回复
-
back stale stale-to-close
难度 2/5 1-3 小时 新手友好度 62/100
npmx-dev/npmx.dev#2511 · 4 条评论 · 1 个 reaction ·
维护者通常 1 天内回复
-
front needs discussion ux
难度 2/5 1-3 小时 新手友好度 65/100
npmx-dev/npmx.dev#2275 · 5 条评论 · 2 个 reaction ·
维护者通常 1 天内回复
查看 npmx-dev/npmx.dev 的全部 Issue
相似的 Issue
-
native
难度 2/5 1-3 小时 新手友好度 72/100
prime-radiant-inc/evener#4839 ·
维护者通常 1 天内回复
-
bug needs-triage
难度 2/5 1-3 小时 新手友好度 70/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 74/100
processone/fluux-messenger#1790 ·
维护者通常 1 天内回复
-
🛣️ Infrastructure
难度 2/5 1-3 小时 新手友好度 65/100
opencrvs/opencrvs-core#14232 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
kunchenguid/gh-axi#220 ·
维护者通常 1 天内回复