Content
@
0 reply
0 recast
0 reaction
horsefacts
@horsefacts.eth
🏃♂️💨 Build a v2 frame NOW speedrun 👉 where to find the repo 👉 how to use the new dev tools 👉 short overview of the frames v2 model See the Github repo here for a full tutorial: https://github.com/farcasterxyz/frames-v2-demo
6 replies
44 recasts
143 reactions
Fucory
@fucory
I wish the default wasn’t next.js because next.js hosted anywhere other than vercel is a disservice to users and onchain wallet based apps fail to take advantage of the next parts of next
2 replies
0 recast
1 reaction
Chris
@chrisdom
might as well use another framework if you plan to neuter the one that blows everything out of the water if you have the right infra for it (sst and opennext, or vercel) use remix or tanstack start, they give the right experience that you're looking for on that note, i'm not sure why @horsefacts.eth used next if 50% was undoing the default settings, why not pick something where you don't have to do this? the people who can sort these issues out in next don't really need a tutorial in the first place.
2 replies
0 recast
0 reaction
horsefacts
@horsefacts.eth
we're focused on shipping the core feature. the goal is to demo how to interact with the SDK. use whatever framework you want, you don't have to use Next. this is a good way to get started *this week*, but I'm sure we'll discover better alternatives as we did with frames v1.
0 reply
0 recast
0 reaction
Fucory
@fucory
Tanstack start is a very bleeding edge and buggy I would not recommend making it a default Remix is a pretty solid choice compared to Next "blows out of the water" is a bit of an exageration. Also opennext isn't quite on par with vercel
0 reply
0 recast
0 reaction
