codesandbox / codesandbox/codesandbox-client
Could not fetch dependencies, please try again in a couple seconds
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
Preflight Checklist
- I have read the [Contributing Guidelines][contributing] for this project.
- I agree to follow the [Code of Conduct][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
Duplicated of #1892, but has not been resolved. Creating an application with my package @arkejs/mui said "Could not fetch dependencies, please try again in a couple seconds: Something went wrong while packaging the dependency INVALID_VERSION"
I saw here https://prod-packager-packages.codesandbox.io/v2/packages/@arkejs/mui/1.0.1.json that is a problem with access of the resource.
A similiar package has not problem: https://prod-packager-packages.codesandbox.io/v2/packages/@arkejs/client/1.1.1.json
How has this issue affected you? What are you trying to accomplish?
To Reproduce
Link to sandbox: https://codesandbox.io/s/arkejs-mui-l319vn)](https://codesandbox.io/s/arkejs-mui-l319vn
Your Environment
| Software | Name/Version |
|---|---|
| Сodesandbox | |
| Browser | Google Chrome 107.0.5304.110 (arm64) |
| Operating System | Apple macOS Monterey M1 Pro - 12.2.1 |
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure in the linked CodeSandbox and compare the package metadata at the @arkejs/mui and @arkejs/client URLs. Trace the dependency packaging path that reports INVALID_VERSION; done means applications can fetch @arkejs/mui dependencies successfully without the error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100