Preview Pane Not Loading in Chrome and Safari

[mcnealjustice98-arch]

Describe the bug

When opening my project in StackBlitz, the preview pane remains blank despite my code being correct. The issue occurs in both Chrome and Safari. The project’s index.html is in the root, all file paths are correct, and external resources are accessible. The preview works only when opening the project in a new browser window, not in the embedded preview pane.

Link to the blitz that caused the error

https://stackblitz.com/edit/stackblitz-starters-hqbljm2h?file=%20index.html

Steps to reproduce

Open StackBlitz project in Chrome or Safari.
Ensure index.html is at the root.
Observe that the preview pane is blank.
Click “Open in New Window” — the project renders correctly.

Expected behavior

When opening the project in StackBlitz, the embedded preview pane should display the website correctly, showing all HTML, CSS, and JavaScript functionality in real time, without requiring the user to open it in a separate browser window.

Parity with Local

• I have run the project in my local machine and I could not reproduce the issue.

Screenshots

Platform

Browser name  = Safari
Full version  = 26.2
Major version = 26
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/26.2 Safari/605.1.15
performance.memory = undefined
Hash = e5af05b3

Additional context

The issue happens in both Chrome and Safari (latest versions).
The project is a simple HTML/CSS/JS setup with index.html at the root.
All file paths and assets are correct, and there are no syntax errors in the code.
The preview works if the project is opened in a new browser window, so the problem seems limited to the embedded preview pane.
Tried clearing cache, using Incognito / Private mode, and disabling browser extensions — the issue persists.
Other StackBlitz projects render fine, suggesting this may be project-specific or a temporary StackBlitz glitch.

[SamVerschueren]

Your package.json is invalid, it does not contain an opening { so it the detection logic doesn't work. If you add that, it works.