Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Missing docs on code splitting #230

Closed
dalechyn opened this issue Apr 5, 2024 · 0 comments
Closed

Missing docs on code splitting #230

dalechyn opened this issue Apr 5, 2024 · 0 comments
Labels
A: Docs Area: Documentation Good First Issue Misc: Good First Issue

Comments

@dalechyn
Copy link
Collaborator

dalechyn commented Apr 5, 2024

Docs currently say nothing about how frog code can be split, yet code splitting is leveraged in the internal playground.

.route('/ui', uiSystemApp)
.route('/fonts', fontsApp)
.route('/middleware', middlewareApp)
.route('/neynar', neynarApp)
.route('/routing', routingApp)
.route('/transaction', transactionApp)
.route('/todos', todoApp)
.frame('/:dynamic', (c) => {

That needs to be documented properly as I've seen many frames implementing unoptimal code-splitting, sometimes even breaking the build (#30), and which can unintentionally cause cyclic dependency issues.

Other refs: https://discord.com/channels/1156791276818157609/1212219334370529370/1225708808484032562

@dalechyn dalechyn changed the title Missing docs on code splitting. Missing docs on code splitting Apr 5, 2024
@tmm tmm added A: Docs Area: Documentation Good First Issue Misc: Good First Issue labels Apr 5, 2024
@tmm tmm closed this as completed Nov 25, 2024
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
A: Docs Area: Documentation Good First Issue Misc: Good First Issue
Projects
None yet
Development

No branches or pull requests

2 participants