My vibe coding a mini app journey so far. Since it's my first time, I wanted to do something very basic like a quiz before I get more advanced

1. used v0.dev to build a nice looking frontend to work with. Found it was so much easier and prettier than just using Cursor directly even with more prompting
2. moved code into Cursor and refined from there since found v0 wasn't as good about refinements I was requesting (especially with guiding me to popular React libraries). Added context with farcaster mini apps and wagmi docs
3. got something basic working locally that I wanted to deploy
4. got stuck on Vercel deploy and been going in loops with Cursor on the cause after pasting in error logs. Got so stuck I just restarted everything over from scratch but then ran into same issues so likely something obvious I need to fix once I try again tomorrow

Shoutout @sophia @maaria for the vibe coding tips

Update: I just got the app to deploy on vercel based on tips people gave me! I followed @fucory's advice on telling Cursor to think harder about the problem vs letting it go in loops, then from @mattlee's advice gave that thinking to another AI which told me what was likely wrong. Once I followed that and fixed, it worked

Next step is to get it published and working specifically as a Farcaster mini app. Then nice to have is to integrate Farcaster social graph using Neynar to make a leaderboard

Was this by a chance the Vercel deploy error? I kept running into this when I tried using the quick start command

Dev ecosystem @farcaster, cofounder @bountycaster. Prev: cofounder of Scalar Capital, product at Coinbase, coproducer @ethereumfilm

I think u just need to await for params and then extract the fid

export default async function Page({
  params,
}: {
  params: Promise<{ fid: string }>
}) {
  const { fid } = await params
}

next js switched to async page params in the v15, docs her

PM by day, hackathons by night | ethglobalexplorer.com, @translate

I think u just need to await for params and then extract the fid

export default async function Page({
  params,
}: {
  params: Promise<{ fid: string }>
}) {
  const { fid } = await params
}

next js switched to async page params in the v15, docs her
https://nextjs.org/docs/app/api-reference/file-conventions/page#props