solidjs-community / solidjs-community/solid-cli
Visible Errors
还没有人认领这个 Issue。
- 主要语言
- TypeScript
- 星标
- 79
- 派生
- 23
- 平均合并
- 2 天 12 小时
- 30 天内合并 PR
- 2
描述
I tried to create a new solid starter project but only got "Something went wrong". It led me here and I upgraded all version of bun, pnpm, node, deno ... etc.
Then I got this at some point:
npx @solid-cli/full create myapp
at Jp (…/.npm/_npx/d471c36726d0a855/node_modules/@solid-cli/full/dist/bin.mjs:8:717)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async lk (…/.npm/_npx/d471c36726d0a855/node_modules/@solid-cli/full/dist/bin.mjs:10:30352)
at async Zh (…/.npm/_npx/d471c36726d0a855/node_modules/@solid-cli/full/dist/bin.mjs:10:30996)
at async I1 (…/.npm/_npx/d471c36726d0a855/node_modules/@solid-cli/full/dist/bin.mjs:10:31079)
at async uf (…/.npm/_npx/d471c36726d0a855/node_modules/@solid-cli/full/dist/bin.mjs:191:296)
at async Object.run (…/.npm/_npx/d471c36726d0a855/node_modules/@solid-cli/full/dist/bin.mjs:220:2605)
at async Vp (…/.npm/_npx/d471c36726d0a855/node_modules/@solid-cli/full/dist/bin.mjs:5:3970)
at async Vp (…/.npm/_npx/d471c36726d0a855/node_modules/@solid-cli/full/dist/bin.mjs:5:3829)
at async zp (…/.npm/_npx/d471c36726d0a855/node_modules/@solid-cli/full/dist/bin.mjs:7:367)
which in turn led me to a fetch to: https://api.github.com/repos/${e}/${t}/commits?per_page=1
and trying this:
curl https://api.github.com/repos/$\{e\}/$\{t\}/commits\?per_page\=1
{"message":"API rate limit exceeded for <my-ip>. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)","documentation_url":"https://docs.github.com/rest/overview/resources-in-the-rest-api#rate-limiting"}
I would have loved to just read the message in the terminal.
So, this is not a bug with the deployments, I assume my office just triggered that rate limit, but it would have been nice to know why "Something went wrong"
贡献指南
这个仓库没有索引到贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
首先重现 npx @solid-cli/full create myapp,并检查请求 https://api.github.com/repos/${e}/${t}/commits?per_page=1 的 CLI 路径;报告的堆栈跟踪指向打包后的 dist/bin.mjs。完成的标准是终端报告底层的 GitHub API 错误,而不是只显示“Something went wrong”。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- github, node.js, typescript
- 领域
- api, cli
- Issue 类型
- 缺陷
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 活跃度
- 停滞
- 描述清晰度
- 基本清楚
- 新手友好度
- 35/100