Templates are private, readme uses the old build system for custom templates
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- nextjs, typescript
Research direction
Start with the README and compare its custom-template guide with the changes in the linked docs/custom-templates-gen branch. Review how the default templates' private visibility should work, then establish a clear, supported workflow for building custom templates and update the documentation accordingly.
Written by the indexing model from the issue text.
Description
The default templates (Nextjs Developer, etc.) are private and cannot be used by other users - although not sure if that's wanted behavior due to possible future updates of the templates itself which could then potentially affect all users of Fragments default templates.
Also the guide uses the old build system mechanism for building custom templates. I have created some changes https://github.com/bxxf/fragments/tree/docs/custom-templates-gen, but it would need some more changes to make it really dev-friendly (the README has been updated and there are scripts to help users automate the process of building their own templates based on the ones in the repo) - see it basically just as a sort of demo, I believe there must be a better way to approach this.
- Dominant language
- TypeScript
- Stars
- 6.4k
- Forks
- 863
- Avg merge
- 15m
- 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 97 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 3/5 1-2 days Newbie friendliness 20/100
-
[Feature Request] Composer SupportMay be free again @mishushakov claimed this 528 days ago, and no pull request is open. OpenFeature Fragments
-
Select element as contextMay be free again @mishushakov claimed this 528 days ago, and no pull request is open. OpenFeature Fragments
All issues in e2b-dev/fragments
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
polarsource/polar#15580 ·
Maintainers usually reply within 1 day
-
accepted bug via-triage
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
pingdotgg/t3code#20931 · 1 comment ·
Maintainers usually reply within 1 day
-
bug/1-unconfirmed kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 83/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
ranxianglei/billion-context#3583 ·
Maintainers usually reply within 1 day