Skip to content

Conversation

@zzq0826
Copy link
Member

@zzq0826 zzq0826 commented Nov 21, 2025

IMPORTANT: Please do not create a Pull Request without creating an issue first.Any change needs to be discussed before proceeding.

Closing issues

closes #ISSUE_NUMBER_GOES_HERE

...

Description

...

Changes

  • High level
  • changes that
  • you made
  • ...

@netlify
Copy link

netlify bot commented Nov 21, 2025

Deploy Preview for scroll-documentation ready!

Name Link
🔨 Latest commit 1ced0db
🔍 Latest deploy log https://app.netlify.com/projects/scroll-documentation/deploys/692001c165edfb0008447181
😎 Deploy Preview https://deploy-preview-542.docs.scroll.xyz
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@vercel
Copy link

vercel bot commented Nov 21, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
scroll-documentation Ready Ready Preview Comment Nov 21, 2025 6:09am

@zzq0826 zzq0826 force-pushed the fix/vercel-build-issue branch from f226cd5 to fc7f1d5 Compare November 21, 2025 03:24
@zzq0826 zzq0826 force-pushed the fix/vercel-build-issue branch from 9c8febb to ec48104 Compare November 21, 2025 04:24
@zzq0826 zzq0826 force-pushed the fix/vercel-build-issue branch from b70ee75 to 4f024d5 Compare November 21, 2025 05:04
@zzq0826 zzq0826 force-pushed the fix/vercel-build-issue branch from 58d1f8a to acaa4b9 Compare November 21, 2025 05:11
@zzq0826 zzq0826 force-pushed the fix/vercel-build-issue branch from 22d79d7 to aa96535 Compare November 21, 2025 05:31
…onents to prevent translation keys from showing in Vercel builds
@zzq0826 zzq0826 force-pushed the fix/vercel-build-issue branch from e56f403 to 1ced0db Compare November 21, 2025 06:07
@zzq0826 zzq0826 merged commit adb6e20 into develop Nov 21, 2025
8 checks passed
zzq0826 added a commit that referenced this pull request Nov 21, 2025
…#542)

* fix: switch Mermaid to client-side rendering for Vercel compatibility

* fix: ensure i18next resources are loaded before rendering client components to prevent translation keys from showing in Vercel builds

---------

Co-authored-by: zzq0826 <[email protected]>
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.

2 participants