fix(docker): fix docker running

[PaiJi]

Summary by CodeRabbit

发布说明

• 重构
  • 项目构建配置已更新为新的文件格式
  • 调整了模块导入方式以适应新的配置结构
  • 构建流程和配置文件引用机制已同步更新以确保兼容性

[coderabbitai]

📝 Walkthrough

Walkthrough

将Next.js配置从TypeScript格式迁移到JavaScript格式。Dockerfile更新COPY步骤，从next.config.ts改为next.config.js。配置文件改用CommonJS导入并移除TypeScript类型注解。

Changes

Cohort / File(s)	Summary
构建配置 Dockerfile	COPY步骤源文件从next.config.ts改为next.config.js，目标路径保持不变。
配置文件转换 next.config.js	将ESM导入语法转换为CommonJS require。移除TypeScript类型注解（NextConfig）。保留核心功能（standalone输出、严格模式、i18n配置）但改为纯JavaScript对象格式。

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• fix(docker): fix docker image build #286：两个PR都修改了Dockerfile中Next.js配置的COPY步骤源文件（一个改为next.config.js，另一个改为next.config.ts），直接影响同一构建制品路径。

Poem

🐰 配置文件换新装，
从TypeScript到JavaScript光，
CommonJS的require声，
编译更快更敞亮，
兔子为此欢欢喜！ ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	标题「fix(docker): fix docker running」过于模糊，使用了重复词「fix docker」且未能清晰表达具体改动，仅说明涉及Docker但缺乏具体修复内容的描述。	建议优化标题为更具体的描述，如「fix(docker): change next.config.ts to next.config.js in Dockerfile」或「fix(docker): convert next.config to CommonJS format」，以清晰反映实际的代码变更内容。

✅ 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 docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/docker-run

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[github-actions]

📦 Next.js Bundle Analysis for furrycons-site

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

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)
/	128.33 KB	478 KB	136.57% (+/- <0.01%)
/404	34.27 KB	383.94 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.78 KB	104.22% (+/- <0.01%)
/city	35.16 KB	384.83 KB	109.95% (+/- <0.01%)
/city/[code]	39.1 KB	388.78 KB	111.08% (+/- <0.01%)
/robots.txt	11.77 KB	361.45 KB	103.27% (+/- <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.