Content
@
https://warpcast.com/~/channel/fbi
0 reply
0 recast
0 reaction
megabyte
@megabyte
https://warpcast.com/megabyte/0x7e5c20d3
2 replies
0 recast
3 reactions
big tone
@bigtone.eth
please help me make mini apps work from ar.io gateways
2 replies
0 recast
1 reaction
megabyte
@megabyte
@samuellhuber.eth is it possible to work with miniapps in a static export of the NextJS? When I try to export it in the static, the server actions like fetching data from @neynar don't work and require need to be made on the client side, which I can't do because of the API Key exposure. Is there any workaround?
1 reply
0 recast
2 reactions
Samuel ツ
@samuellhuber.eth
NextJS Server actions maybe what screws you here That’s NextJs related and not a mini app / neynar bug I‘d search NextJS docs here to figure it out. Since we don’t use NextJS server actions and only advise NextJS usage if you host on vercel I sadly don’t have much more input here without trying to debug your code directly besides untangle server actions into traditional Frontend -> backend calls
2 replies
0 recast
2 reactions
0xbhaisaab
@0xbhaisaab
yeah, easiest workaround would be to create an api that takes data from neynar and provide that to your getServersideProps. getServersideProps ar enot meant to use third party apis directly.
1 reply
0 recast
3 reactions
Samuel ツ
@samuellhuber.eth
sir, just frontend -> Backend :D just call your own API e.g. /api/neynar/serveXZY or if you want to be even easier. since neynar auth is a cache header you could just setup a proxy adding the Auth bearer to all calls and you proxy the calls and just call neynar directly, no need for setting up any server side logic
2 replies
0 recast
2 reactions
0xbhaisaab
@0xbhaisaab
that makes sense, but i think the static export might require getserversideprops functions. have not tried server components with static export.
1 reply
0 recast
1 reaction
Samuel ツ
@samuellhuber.eth
why server components there? it's static? so you don't render on server?
0 reply
0 recast
1 reaction
