Content
@
https://opensea.io/collection/neynar-1
0 reply
0 recast
0 reaction
jp 🎩
@jpfraneto.eth
initial feedback: 1. love the flow of doing it like this. thank you 2. below the "lets create your frame" it would be helpful to know the tech stack it will have (maybe even choose it like when you create an app with vite) 3. at the seed phrase phase i would rather scan a qr code than copy pasting my seedphrase (but idk if this can be done tbh) 4. the url changes every time i run "npm run dev". imo it needs to be the same one all the time. if not it is too much mental pain to change it and paste in the IP every time i start the dev env again. maybe im too used to use ngrok with the same url tho 5. the frame is not loading on the dev tools. i followed the instructions of the console but it is taking more than 10s. on the browser it loads after a while i realized that it is not loading because the Demo component (where the sdk.actions.ready() is called) is not used directly on the page.tsx. i fixed that and now it works. i also had to import the Providers on the layout.tsx which was not done automatically
3 replies
0 recast
4 reactions
rish
@rish
@jpfraneto.eth I haven’t run into #5 on my end so might have more questions on that later
1 reply
0 recast
1 reaction
jp 🎩
@jpfraneto.eth
i started a new project with this to test that out again and i confirm that it is still the case left is the frame, right is on browser. the changes i would do are: 1. import the Demo component (or similar) on src/app/page.tsx so that the route that is loaded when the frame starts (by default on the "/" route) calls the sdk.actions.ready() function, which is what inhibits the frame from loading on the left image. or create a useEffect on the layout.tsx that does this 2. import the Providers on layout.tsx and wrap the app on this so that everything works properly im not 100% sure but probably this would make the frame be rendered "out of the box" and on the first run of the instructions that appear the first time you run "npm run dev" after everything ends installing
2 replies
0 recast
0 reaction
veganbeef
@veganbeef
It looks like there might be some cached files being used somewhere they shouldn't. Could you confirm by restarting your terminal, running "npm cache clean --force", and then trying the latest script version please? You should then have code in your repo that reflects the latest files in the repo e.g. layout.tsx should import and configure providers, etc.
1 reply
0 recast
1 reaction
jp 🎩
@jpfraneto.eth
ok will try when im back to the keyboard and report. thank you
0 reply
0 recast
1 reaction
