Tony D’Addeo
@deodad
frame devs: what do you prefer about the frames.js frame debugger over the warpcast debugger?
7 replies
4 recasts
17 reactions
matt 💭
@matthewmorek
warpcast debugger: - is wonky - loses all my input on reload (unlike Warpcast mobile) - it doesn't debug anything, just launches a frame - throws errors on SDK interactions (add frame) instead of helping me debug them (success/failure) - it's necessary evil since it's the only way to simulate FC connection what I'd like as a developer: - support debugging SDK interactions - save my input to local storage, so I don't have to re-type it each time - output extra Warpcast-specific stuff to console: auth, connection, interactions, etc - output some basic stats (time to auth, etc) oh, and above all: fix timeout when trying to fetch frame embedding
1 reply
0 recast
4 reactions
Kasra Rahjerdi
@jc4p
1. being able to do it locally without ngrok or a tunnel 2. impersonating diff FIDs 3. the console.log output in the chrome inspector
1 reply
0 recast
6 reactions
limone.eth 🍋
@limone.eth
frames.js allows me to debug locally without the need of tunneling
0 reply
0 recast
4 reactions
keccers
@keccers.eth
Runs locally Shows the meta response and what if any parts of that are messed up very clearly Bundles in feed preview + launch preview — more realistic e2e exp
0 reply
0 recast
4 reactions
Linda Xie
@linda
cc @dish @colin @ba @n if you have any input
2 replies
0 recast
4 reactions
Ben Adamsky 💭
@ba
@matthewmorek I know you have a lot of input here
0 reply
0 recast
1 reaction
kompreni 🚂
@kompreni
Havent used the frames.js debugger. Will check it out! Warpcast debugger is "good enough" for me rn imo
0 reply
0 recast
0 reaction
