codesandbox / codesandbox/codesandbox-client
Whether to support api creation of `devbox`
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
How has this issue affected you? What are you trying to accomplish?
To Reproduce
There is this sentence in the document, which states that it supports using api to create devbox, but I followed the instructions and created it without success.
and I saw the defender's answer here
But I saw in a repo that this method could use the api to create a devbox, but it was unstable after I tested it. One of the five creations might stay in the sandbox, causing the example to fail.
So what should I do to successfully use the api to successfully run the project created by vite on codesandbox.😟😟😟
Your Environment
| Software | Name/Version |
|---|---|
| Сodesandbox | latest |
| Browser | 129.0.6668.60 (64 位) |
| Operating System | Windows 11 x64 |
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 with the "Programmatically creating Devboxes" documentation page and the referenced utils/buildVue3Sandbox.js example at line 83. Reproduce the Vite project creation flow and compare the documented API behavior with the example's intermittent failures. Done means the API flow is reliable and documented accurately, or the documentation clearly states its limitation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, vite
- Domain
- api, documentation
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100