Bug: Errors appear in the browser console immediately on lexical.dev page load

[Deepmalya1]

Bug description

When visiting https://lexical.dev, multiple errors appear in the browser console immediately on page load, including network failures, analytics script errors, and a recoverable React error thrown by the Docusaurus React root.

These errors occur without any user interaction and appear to be related to third-party scripts (Facebook static docs ping, Vercel analytics, and StackBlitz embeds) failing to load or being misconfigured.

---

Lexical version

N/A – issue observed on the official Lexical documentation site (https://lexical.dev), not in a local Lexical project.

---

Steps To Reproduce

1. Open https://lexical.dev in a browser (tested in Chrome).
2. Open DevTools → Console.
3. Observe errors and warnings logged immediately after page load.

---

Link to code example

N/A – issue occurs directly on the official documentation website.

---

The current behavior

The following errors and warnings are logged in the console:

• Network errors:
  • staticdocs.thefacebook.com/ping: Failed to load resource: net::ERR_NAME_NOT_RESOLVED
• React error:
  • Docusaurus React Root onRecoverableError: Error: Minified React error #418
• Analytics-related errors:
  • /_vercel/insights/script.js: 404
  • [Vercel Web Analytics] Failed to load script
• StackBlitz embed error:
  • Script refused to execute due to incorrect MIME type (text/html)
• Warnings about preloaded but unused worker resources

These errors occur consistently on every page load.

---

The expected behavior

• The Lexical documentation site should load without emitting React errors in the console.
• Third-party scripts (analytics, embeds, tracking pings) should either load correctly or fail gracefully without triggering React errors.
• A normal page load should not produce console errors.

---

Impact of fix

• Severity: Low to medium
• Frequency: Always reproducible
• Impact:
  • Creates noise for developers inspecting the documentation
  • Makes it harder to distinguish real application issues from documentation errors
  • May reduce confidence when evaluating Lexical based on the documentation site

Fixing this would improve developer experience for anyone visiting or debugging the Lexical documentation.

[etrepum]

No need for assignment, simply create a PR when you have something to contribute.