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

Dependency count and bundle size increases are time-based, but should compare to nearest applicable version

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
54/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
nuxt, typescript

调研方向

Start by locating the code that generates dependency count and bundle size warnings and read how it chooses the comparison release. Reproduce the Storybook 11 alpha and backport case, then trace how semver could select the nearest applicable version. Done means both warnings compare against the expected release for the examples in the issue.

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

描述

pending triage
Describe the bug

We believe the dependency count and bundle size warnings are based off release timing, leading to comical comparisons when a team releases bug fixes with backports :)

For instance here, we released a Storybook 11 alpha alongside 3 security backports for 8, 9 and 10. Storybook 11.0 a6 is compared to Storybook 9 but comparing to 11.0 a5 would make more sense.

Image

Here Storybook 9 is compared to Storybook 8, even though the storybook 8 package was an empty shell back in the day.

Image
Additional context

I think comparing to the previous semantic release would fix that. A X.0.0 major could compare to the previous stable release, but patch and minor releases would naturally compare to the code in their branch if doing based on semver.

Logs

主要语言
TypeScript
星标
3.6k
派生
533
平均合并
5 天 1 小时
30 天内合并 PR
36

环境准备

这个项目没有提供开发容器、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 摘要。