Content pfp
Content
@
https://warpcast.com/~/channel/frames-devs
0 reply
0 recast
0 reaction

onten.eth | β“‚οΈπŸ–πŸŽ© pfp
onten.eth | β“‚οΈπŸ–πŸŽ©
@rezaisgoat.eth
I code my frames using frog and I have problem with using my modules. I import them like this an also turned on this option in my tsconfig allowImportingTsExtensions things work fine locally with dev server, but I have problem with the deployment. is it my code or frog? https://warpcast.com/rezaisgoat.eth/0x9a3d1134
4 replies
0 recast
3 reactions

conca πŸŽ©πŸ’» pfp
conca πŸŽ©πŸ’»
@0xconca.eth
Same boat, don’t understand how only a handful of people is complaining. I resolved by switching to Firebase Cloud Functions: had to write my own Handler from scratch but it was so worth it!
1 reply
0 recast
1 reaction

onten.eth | β“‚οΈπŸ–πŸŽ© pfp
onten.eth | β“‚οΈπŸ–πŸŽ©
@rezaisgoat.eth
I got another Q non related to this. What is the resolution of the images you're returning to the user? I was reading frames.js docs and it says images should stay below 250kB. Is it a must for the opengraph protocol? Cuz I used to return 800kB 1080x1080 images with frog.
1 reply
0 recast
0 reaction

conca πŸŽ©πŸ’» pfp
conca πŸŽ©πŸ’»
@0xconca.eth
There’s a difference between returning the image as HTML/JSX and passing the url of a converted image! The former needs to be <250kb and the latter can be even 10MB! That’s why I convert every response to png before returning it, it’s an extra step but it ensures more flexibility
1 reply
0 recast
1 reaction

onten.eth | β“‚οΈπŸ–πŸŽ© pfp
onten.eth | β“‚οΈπŸ–πŸŽ©
@rezaisgoat.eth
Wow. I thought the frameworks like frog and frames.js convert the JSX to png themselves and send that PNG to the client! How do you do that extra step? I feel like getting into a rabbit hole now.πŸ˜‚
1 reply
0 recast
0 reaction