codesandbox / codesandbox/codesandbox-client

Chrome Errors in project preview "TypeError Could not fetch dependencies, please try again in a couple seconds"

Open
#6,825 13 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
13.6k
Forks
2.4k
Avg merge
6d 19h
Merged PRs (30d)
2

Description

🐛 bug report

Edit: updated link to reflect new location:

Preflight Checklist

  • I have read the Contributing Guidelines for this project.
  • I agree to follow the Code of Conduct that this project
    adheres to.
  • I have searched the issue tracker for an issue that matches the one I want
    to file, without success.

Description of the problem

Under Chrome, the sandbox located here produces an error in the embedded browser:

https://codesandbox.io/s/github/akutruff/diagon/tree/master/apps/demo

Firefox works fine.

TypeError
Could not fetch dependencies, please try again in a couple seconds: Cannot read properties of null (reading 'match')
s
https://codesandbox.io/static/js/sandbox.11a2ae9a6.js:1:138474
(anonymous function)
https://codesandbox.io/static/js/sandbox.11a2ae9a6.js:1:170761
i
https://codesandbox.io/static/js/sandbox.11a2ae9a6.js:1:167040

How has this issue affected you? What are you trying to accomplish?

Project broken in chrome.

To Reproduce

Go to sandbox here: https://codesandbox.io/s/github/akutruff/diagon/tree/master/apps/demo and try to see the app.
If you copy the embedded preview url into a new browser tab, the error will also occur. If you "empty cache and hard reload" on the tab with the preview url, it will actually work once. If you refresh that page again, the error occurs again. "empty cache and hard reload" on the full sandbox does not fix the problem.

Link to sandbox: link (optional)
Your Environment
Software Name/Version
Сodesandbox latest
Browser Chrome
Operating System Windows

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the failure at the linked CodeSandbox project preview in Chrome, then compare it with Firefox and the embedded preview URL in a new tab. The work is done when the demo preview loads reliably in Chrome, including after refresh, without the reported dependency-fetch error.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.