Skip to content

fix(docker): fix docker image build#286

Merged
PaiJi merged 1 commit intomainfrom
fix/docker-build
Feb 4, 2026
Merged

fix(docker): fix docker image build#286
PaiJi merged 1 commit intomainfrom
fix/docker-build

Conversation

@PaiJi
Copy link
Member

@PaiJi PaiJi commented Feb 4, 2026

Summary by CodeRabbit

发布说明

  • Chores
    • 更新了构建配置以改进技术基础设施。

@coderabbitai
Copy link

coderabbitai bot commented Feb 4, 2026

📝 Walkthrough

概览

Dockerfile 中的生产镜像配置文件源从 JavaScript 格式(next.config.js)变更为 TypeScript 格式(next.config.ts),目标位置保持不变为 ./next.config.ts

变更

Cohort / File(s) 摘要
配置文件格式转换
Dockerfile
将复制指令中的 Next.js 配置源从 .js 更新为 .ts,以适应 TypeScript 配置文件格式。

代码审查工作量

🎯 1 (简单) | ⏱️ ~3 分钟

诗歌

从 .js 到 .ts 的小转变,
配置文件换新装,
兔子欢呼跳三跳,
TypeScript 让项目更闪亮! 🐰✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1
❌ Failed checks (1 inconclusive)
Check name Status Explanation Resolution
Title check ❓ Inconclusive PR标题虽然提到了docker image build问题,但措辞模糊,未明确指出具体修复内容(从.js到.ts配置文件的切换)。 建议更新标题为更具体的描述,例如'fix(docker): switch Next.js config from .js to .ts'或'fix(docker): update Next.js config file extension',以更清楚地传达实际的变更内容。
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch fix/docker-build

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions
Copy link

github-actions bot commented Feb 4, 2026

📦 Next.js Bundle Analysis for furrycons-site

This analysis was generated by the Next.js Bundle Analysis action. 🤖

⚠️ Global Bundle Size Increased

Page Size (compressed)
global 349.68 KB (🟡 +7 B)
Details

The global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

If you want further insight into what is behind the changes, give @next/bundle-analyzer a try!

Nine Pages Changed Size

The following pages changed size from the code in this PR compared to its base branch:

Page Size (compressed) First Load % of Budget (350 KB)
/404 34.27 KB 383.95 KB 109.70% (+/- <0.01%)
/500 34.26 KB 383.94 KB 109.70% (+/- <0.01%)
/[organization] 47.36 KB 397.04 KB 113.44% (+/- <0.01%)
/[organization]/[slug] 100.59 KB 450.26 KB 128.65% (+/- <0.01%)
/about 15.11 KB 364.79 KB 104.22% (🟡 +0.01%)
/city/[code] 39.11 KB 388.78 KB 111.08% (+/- <0.01%)
/organization 44.08 KB 393.76 KB 112.50% (+/- <0.01%)
/robots.txt 11.77 KB 361.45 KB 103.27% (+/- <0.01%)
/years 48.5 KB 398.18 KB 113.77% (+/- <0.01%)
Details

Only the gzipped size is provided here based on an expert tip.

First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

The "Budget %" column shows what percentage of your performance budget the First Load total takes up. For example, if your budget was 100kb, and a given page's first load size was 10kb, it would be 10% of your budget. You can also see how much this has increased or decreased compared to the base branch of your PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this. If you see "+/- <0.01%" it means that there was a change in bundle size, but it is a trivial enough amount that it can be ignored.

@PaiJi PaiJi merged commit dcb95c5 into main Feb 4, 2026
8 checks passed
@PaiJi PaiJi deleted the fix/docker-build branch February 4, 2026 10:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant