codesandbox / codesandbox/codesandbox-client
DependencyNotFoundError for a repository that is built on my local machine
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 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
I created a sandbox from an existing GitHub repository. It's a react project. It can be built and run on my local machine, but it fails on codesandbox.
How has this issue affected you? What are you trying to accomplish?
I'm trying to create a sample for the react team, because I think they have a bug, or at least they can improve their codebase. While my sample runs on my local machine, it fails to start on codesandbox.io
To Reproduce
Please see this code sandbox:
https://codesandbox.io/s/holismreact-infra-nh1b4
Link to sandbox: link (optional)
Your Environment
| Software | Name/Version |
|---|---|
| Сodesandbox | |
| Browser | Chrome 94.0.4606.71 (Official Build) (64-bit) |
| Operating System | Ubuntu 20.04 |
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 from the linked CodeSandbox and comparing it with the referenced repository's successful local build. Trace the DependencyNotFoundError through the dependency-loading path; done means the sandbox starts the React project successfully without breaking local builds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- devtools, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100