codesandbox / codesandbox/codesandbox-client
Repository created with empty code
Open
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
When creating a new repo, it redirects to the new editor,
then after the installation is done, it demands
We are enable to detect target browsers
How has this issue affected you? What are you trying to accomplish?
I want to create a new repo with existing code
To Reproduce
- open https://codesandbox.io/s/03duwm?file=/demo.tsx
- Signin
- Fork the repo
- Create repository
- Open it to GitHub
Link to sandbox: [link](here) (optional)
Your Environment
| Software | Name/Version |
|---|---|
| Сodesandbox | d910f64 |
| Browser | Chrome |
| Operating System | Windows |
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 GitHub repository creation flow from the linked CodeSandbox example in Chrome on Windows, then inspect the new editor and repository-creation entry points involved. Done means the existing code is retained in the created repository and the target-browser detection error no longer blocks the flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- developer-experience
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100