feat: resolve the 404 page issue

[wuyiping0628]

Summary by CodeRabbit

• Chores
  • Updated build configuration for improved asset handling and documentation management.
  • Enhanced image format support in the asset pipeline.
  • Updated project dependencies.

[coderabbitai]

Walkthrough

VitePress configuration updated to disable dead link checking, expand markdown file exclusions, configure image asset handling for various formats in Vite, and add a new @demos path alias. Additionally, the tiny-engine submodule pointer is advanced to a newer commit revision.

Changes

Cohort / File(s)	Summary
VitePress Configuration .vitepress/config.mts	Added ignoreDeadLinks: true to disable dead link validation; expanded srcExclude to exclude additional markdown variants (README*.md, develop-demo-en.md, theme-en.md); added assetsInclude in Vite config to treat image formats (including uppercase extensions) as assets; added @demos alias in Vite resolve configuration
Submodule Update tiny-engine	Submodule pointer updated from commit 79cbf42d to ed68aa3ca7e19d

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

• Configuration changes are straightforward property additions and extensions with clear intent
• Submodule update is routine maintenance with no code logic to review
• Minimal risk of unintended side effects given the nature of configuration adjustments

Poem

🐰 Through config files we hoppy go,
Dead links ignored, exclusions grow,
Assets handled, demos near,
Tiny-engine advances here! ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'resolve the 404 page issue' is vague and doesn't clearly describe the specific technical changes made to address the issue.	Consider a more descriptive title that explains what was changed, such as 'fix: ignore dead links and configure asset handling in VitePress config' to better convey the actual modifications.

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

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

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.}

[coderabbitai]

Actionable comments posted: 2

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1d15a8d and 6b2cb39.

📒 Files selected for processing (2)

• .vitepress/config.mts (2 hunks)
• tiny-engine (1 hunks)

🔇 Additional comments (3)

tiny-engine (1)

1-1: The original review comment is incorrect—the configuration file was actually modified.

The git diff confirms that both .vitepress/config.mts and tiny-engine (submodule) were modified in this PR. The original review incorrectly assumed the config file was not changed; in fact, all the changes mentioned in the AI summary are present:

• ignoreDeadLinks: true — directly addresses 404 errors by preventing the build from failing on dead links
• srcExclude expanded — filters out English demo files (develop-demo-en.md, theme-en.md)
• assetsInclude added — ensures image assets with uppercase extensions are properly handled, preventing import-analyze from treating them as JavaScript
• @demos alias added — provides correct path resolution to demo files (../../tiny-vue/examples/sites/demos/pc)

These changes form a coherent solution for the PR objective to resolve the 404 page issue. The submodule update pairs with these configuration changes to enable proper asset handling and path resolution.

Likely an incorrect or invalid review comment.

.vitepress/config.mts (2)

43-44: Good addition for handling uppercase image extensions.

This configuration ensures that image files with uppercase extensions are correctly treated as static assets rather than being incorrectly parsed as JavaScript modules. This is a proper fix for potential build issues.

---

39-39: Line 39 (srcExclude) was not modified in this PR.

The srcExclude configuration is identical in the base branch (HEAD) and the current PR branch. This review comment appears to target a line that was not changed by these modifications. If srcExclude patterns require attention, that should be addressed in a separate review or PR focused on configuration improvements.

Likely an incorrect or invalid review comment.