frame devs: what do you prefer about the frames.js frame debugger over the warpcast debugger?

Founder far.quest & @wieldlabs.eth. Investing miy.com ventures. FID #274. Previously Square/Cash App. https://hiimnico.xyz/

cma.xyz. Founder /paragraph, ceo /mirror, previously at Google & Coinbase 

co-founder @ponder @survey // benadamsky.com

Building @warpcast and @farcaster / dad / like to read, cook, ski, code

cc @dish @colin @ba @n if you have any input

Developer ecosystem @farcaster, co-founder @bountycaster. Previously: co-founder of Scalar Capital, product at Coinbase, co-producer @ethereumfilm

Would be nice if it displays a list of metadata it fetched so it’s easier to debug - the errors are hard to debug like “missing image” or sometimes the title is just too long

Never used the frames.js debugger so I don't have any input

I've struggled quite a bit with the Warpcast debugger though; I casted reasons why when we launched the v2 frame