Content pfp
Content
@
0 reply
0 recast
0 reaction

Darryl Yeo đŸ› ïž pfp
Darryl Yeo đŸ› ïž
@darrylyeo
Next.js → Astro migration successful! 🚀 https://github.com/fluidkey/walletbeat/pull/104 https://warpcast.com/polymutex.eth/0xdea98ef2
3 replies
1 recast
27 reactions

Nate pfp
Nate
@natedev.eth
when astro frames
3 replies
0 recast
4 reactions

Steve pfp
Steve
@sdv.eth
cc @iammatthias
1 reply
0 recast
2 reactions

matthias pfp
matthias
@iammatthias
repo is out of date, but it's pretty straight forward https://github.com/iammatthias/simple-astro-frame
1 reply
0 recast
4 reactions

Nate pfp
Nate
@natedev.eth
that's a v1 frame right? I know nothing about v2, so idk how different it is
1 reply
0 recast
2 reactions

matthias pfp
matthias
@iammatthias
yeah, this is v1. @stevedylandev.eth has a solid v2 tutorial that should work nicely for Astro https://orbiter.host/blog/how-to-deploy-a-v2-frame-on-orbiter
1 reply
0 recast
3 reactions

Steve pfp
Steve
@stevedylandev.eth
Yup! I need to experiment more with a rudimentary V2 Astro frame. Our marketing site is a minimal V2 frame but I’d like to add more functionality using the SDK, which might just end up being a react component inside Astro
2 replies
0 recast
4 reactions

Nate pfp
Nate
@natedev.eth
honestly I don't mind having react islands, I still think that using astro as a react framework is worth it
2 replies
0 recast
2 reactions

Steve pfp
Steve
@stevedylandev.eth
100%
0 reply
0 recast
0 reaction

matthias pfp
matthias
@iammatthias
tbh I struggle with frameworks in Astro. Islands are a cool concept, but they feel clunky whenever I write one. Would rather just use Vite at that point.
1 reply
0 recast
2 reactions