Image is broken on the main page of `docusaurus.io/docs`

[BorysShulyak]

Have you read the Contributing Guidelines on issues?

• I have read the Contributing Guidelines on issues.

Prerequisites

• I'm using the latest version of Docusaurus.
• I have tried the npm run clear or yarn clear command.
• I have tried rm -rf node_modules yarn.lock package-lock.json and re-installing packages.
• I have tried creating a repro with https://new.docusaurus.io.
• I have read the console error message carefully (if applicable).

Description

The 'Introduction' image is broken on the main page of docusaurus.io/docs

Reproducible demo

https://jam.dev/c/93a4e007-e162-4976-935f-efd37bc0ec48

Steps to reproduce

• Open docusarus docs main page
• See the broken image.

Expected behavior

The image should be successfully loaded.

Actual behavior

The image is not loaded.

Your environment

• Public source code: https://github.com/facebook/docusaurus/tree/main/website
• Public site URL: https://docusaurus.io/docs
• Docusaurus version used: latest

System:
OS: macOS 14.1.2
CPU: (10) arm64 Apple M1 Pro
Memory: 109.31 MB / 16.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 20.9.0 - ~/.nvm/versions/node/v20.9.0/bin/node
npm: 10.1.0 - ~/.nvm/versions/node/v20.9.0/bin/npm
pnpm: 8.14.3 - ~/.nvm/versions/node/v20.9.0/bin/pnpm
Browsers:
Brave Browser: 128.1.69.162
Chrome: 129.0.6668.71
Safari: 17.1.2

Self-service

• I'd be willing to fix this bug myself.

[Josh-Cena]

Thanks, but it's not broken for me and for others. Perhaps it's a network connection issue or a transient issue with Netlify, but it's not actionable on our side.

[slorber]

I also noticed images being broken randomly on our site and deploy previews.

The problem you saw was probably there indeed and it's a real bug, but it may have been fixed by a prod redeploy. (although it's surprising, there has been no redeploy since you posted the bug, maybe you recorded the video earlier?)

Here's an older prod deployment with the problem:
https://66f6f046a744c2b4a99366bc--docusaurus-2.netlify.app/docs

This is a bug introduced in #10479 related to Webpack inline loaders using randomly emit=true or emit=false, that was already my plan to investigate this right now!