frames-devs

hey @awkweb I got an issue in regards of importing a self-written module to the index.tsx file.
the module I use is in the same directory as index.tsx and everything works fine while developing on local, but when I deploy on Vercel things go wrong and placing the content of the modules on top of everything fixes it.

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?

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

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!

💻 building /hyperclient && @atlas && @gif composer action (check bio for details) | 👑 support me and @gif project by subbing to https://hypersub.xyz/s/gif

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.

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.😂

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