README demo GIF is 7.7 MB

未关闭 适合新手
#157 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
86/100
Issue 类型
重构
描述清晰度
描述清楚
活跃度
活跃
技术栈
javascript
领域
performance

调研方向

从 README.md:131 中的演示引用和源文件 assets/screenshots/play-vs-computer.gif 开始。检查图像尺寸和帧率,然后比较压缩选项,同时确认片段仍然展示与电脑对战的游戏。README 中的演示小于约 1.5 MB 且仍然易于理解时,即为完成。

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

描述

good first issue performance severity: low

Summary

assets/screenshots/play-vs-computer.gif, added in the latest commit and embedded in the README, is 7.7 MB. That is about 80% of assets/.

Where

  • README.md:131
  • assets/screenshots/play-vs-computer.gif (7,870,061 bytes)

Impact

Every README view on GitHub downloads about 7.7 MB, which takes seconds on mobile. Every clone carries the file permanently in history, and the Pages deploy publishes it too. The app itself does not download it: the file is not in the service worker's file list.

Suggested fix

Reduce the frame rate, colours or dimensions to stay under about 1.5 MB, or use an MP4/WebM clip, which is usually about 10x smaller. GitHub READMEs can show a video uploaded as an asset. Replace the file soon, before more history accumulates.

Acceptance criteria

  • The README demo is under ~1.5 MB and still shows a game against the computer

Getting started

  • Relevant files: README.md, assets/screenshots/

Filed by repo-audit/full-audit at 73cd279. Severity: low. Effort: S. audit-key: performance|assets/screenshots/play-vs-computer.gif|readme-gif

主要语言
JavaScript
星标
4
派生
2
平均合并
6 小时 13 分钟
30 天内合并 PR
4

环境准备

从这里开始

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

TMHSDigital/Static_Chess 的其他 Issue

查看 TMHSDigital/Static_Chess 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

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