the result can't be seen
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 20/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- web-dev
Research direction
The issue names no files, tests, or entry points and provides only an attached screenshot. Start by reviewing the screenshot and reproducing the case in the application, then trace the relevant result-display flow. Done means the result is visible in the reported scenario and the behavior is covered by an appropriate check.
Written by the indexing model from the issue text.
Description
- Dominant language
- TypeScript
- Stars
- 6.4k
- Forks
- 863
- Avg merge
- 16m
- Merged PRs (30d)
- 4
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from e2b-dev/fragments
-
Sandbox route: forEach(async) fire-and-forget can run code before multi-file writes finishPossibly taken @Prasad48432 claimed this 116 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Dependency DashboardOpen
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
[Feature Request] Composer SupportMay be free again @mishushakov claimed this 546 days ago, and no pull request is open. OpenFeature Fragments
-
Select element as contextMay be free again @mishushakov claimed this 546 days ago, and no pull request is open. OpenFeature Fragments
All issues in e2b-dev/fragments
Similar issues
-
cloudflare-cache-binding: `unstorage://` keys are rejected by the Cache API, cache never storesOpen
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 2 days
-
reproduced
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
anomalyco/opencode#62052 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
strapi/design-system#2084 ·
Maintainers usually reply within 3 days
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day