Staging

[afsar-dev]

Summary by CodeRabbit

• Improvements

  • Enhanced compiler reliability with multi-URL fallback strategies for loading WebAssembly components, ensuring better resilience during playground initialization.
  • Added timeout protection for WebAssembly binary fetching to prevent indefinite waits during compilation startup.

• Chores

  • Updated dependency resolution constraints.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
nurui	Building	Preview, Comment, Open in v0	Apr 3, 2026 2:01pm

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: bfba5fcd-a49e-4c58-9969-fc9ddf522f0e

📥 Commits

Reviewing files that changed from the base of the PR and between 5f16664 and c6af90c.

⛔ Files ignored due to path filters (1)

• yarn.lock is excluded by !**/yarn.lock, !**/*.lock

📒 Files selected for processing (2)

• package.json
• src/features/playground/core/compiler.ts

---

📝 Walkthrough

Walkthrough

The changes update esbuild WASM initialization to support in-browser compilation with a multi-CDN fallback strategy for robustness, while removing a specific minimatch version constraint from dependency resolutions.

Changes

Cohort / File(s)	Summary
Package dependencies package.json	Removed minimatch version resolution constraint (^9.0.5).
esbuild WASM initialization src/features/playground/core/compiler.ts	Added fetchWasmModule() for in-browser WASM compilation with timeout support via AbortController. Added initializeEsbuildWithFallbacks() to attempt initialization from multiple CDN sources (unpkg and jsdelivr) with consolidated error reporting. Modified ensureInitialized() to use the new fallback strategy instead of direct wasmURL initialization.

Sequence Diagram

sequenceDiagram
    participant Browser
    participant CDN1 as unpkg CDN
    participant CDN2 as jsdelivr CDN
    participant WASM as WebAssembly
    participant esbuild

    Browser->>Browser: ensureInitialized()
    Browser->>Browser: initializeEsbuildWithFallbacks()
    
    Browser->>CDN1: Fetch esbuild.wasm (unpkg)
    CDN1-->>Browser: Response
    alt Success
        Browser->>WASM: WebAssembly.compile()
        WASM-->>Browser: Module
        Browser->>esbuild: esbuild.initialize({ wasmModule })
        esbuild-->>Browser: Ready
    else Fetch/Compile Failed
        Browser->>CDN2: Fetch esbuild.wasm (jsdelivr)
        CDN2-->>Browser: Response
        alt Success
            Browser->>WASM: WebAssembly.compile()
            WASM-->>Browser: Module
            Browser->>esbuild: esbuild.initialize({ wasmModule })
            esbuild-->>Browser: Ready
        else All Failed
            Browser-->>Browser: Throw consolidated error
        end
    end

Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~15 minutes

Poem

🐰 With whiskers twitching, I celebrate today,
WASM downloads now have fallback's sway!
From unpkg to jsdelivr we skip,
When one CDN stumbles, the other won't trip. ✨
A safer compiler, faster and bright! 🚀

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch staging

---

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