gitlab stricter api rate limits announced
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 45/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- gitlab, nuxt, typescript
- 领域
- api
调研方向
Start by locating the GitLab API calls used for package metadata and changelogs, then read how metadata currently uses cachedfetch and how changelog fetching will use defineCachedFunction. The issue lists access tokens and a separate GitLab API fork as possible approaches, but does not choose one. Done should include an agreed approach that reduces rate-limit risk while supporting the mentioned GitLab data.
由索引模型根据 Issue 内容生成。
描述
context
Gitlab has announced they're going to make some changes to their api rate limits rules.
From 19th of October an unauthenticated requests will be rate limited to 60 requests per hour per ip.
with a free account with an access token the request go to 5000 request per account.
Currently npmx uses the gitlab api to get metadata (ex: stars), latest release & releases list api's.
link to announcement blog post: https://about.gitlab.com/blog/rate-limit-change-2026/
possible solutions
- Add via environment variables Gitlab access token(s)
- possibly make the access token available via a function to allow easier changes in only 1 function
- create an fork of ungh that serves the gitlab api instead of github's (ungl)
further unless ungl gets made, it would be best if gitlab api is used via cachedfetch or defineCachedFunction to reduce refetching the same data
For package changelog I'll add defineCachedFunction to reduce refetching the same data.
Getting metadata like stars already use cachedfetch currently
if there other solutions or you've some opinions, then don't be hesitant to comment below.
I know that Gitlab isn't used as much as for example github for hosting npm packages source code, but it might still be best to be able to handle more than 60 an hour
- 主要语言
- TypeScript
- 星标
- 3.6k
- 派生
- 533
- 平均合并
- 4 天 13 小时
- 30 天内合并 PR
- 37
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
npmx-dev/npmx.dev 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 68/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
-
bug
难度 2/5 1-3 小时 新手友好度 76/100
cloudscape-design/components#5184 ·
维护者通常 2 天内回复
-
enhancement
难度 2/5 1-3 小时 新手友好度 75/100
JarX-Concepts/react-native-platform-components#130 ·
维护者通常 1 天内回复
-
fix(api): optimize-for-web /preview outer catches miss asDecoderOutOfMemory on V8 OOM and SIGKILL未关闭area: backend bug priority: low
难度 2/5 1-3 小时 新手友好度 83/100
snapotter-hq/SnapOtter#3773 ·
维护者通常 1 天内回复
-
ai-driven-qa ux-audit
难度 2/5 1-3 小时 新手友好度 78/100
linagora/twake-contacts-frontend#386 ·
维护者通常 1 天内回复
-
git: README should state plainly that without --repository every reachable repository is in scope未关闭documentation server-git v2
难度 1/5 1-3 小时 新手友好度 84/100
modelcontextprotocol/servers#5225 ·
维护者通常 1 天内回复