Building FOSS via @frames, /open-frames to help decentralized social win. a16z CSX23. farcasterchannels.com farcaster.id

cypherpunk wannabe, engineer working on @frames /open-frames /opencast
https://stephancill.co.za create stories at https://stories.steer.fun

hey @df @stephancill i was having issues with the frames.js debugger, so i started fresh with a new repo clone and followed the "framesjs-starter" example readme and am still getting:

Module not found: Can't resolve 'frames.js/next/server'
> 1 | import {
  2 |   FrameButton,
  3 |   FrameContainer,
  4 |   FrameImage,

because knowing is finding the limits /outercorps

actually, if you extract the example away from the parent repo, remove all build dirs and node_modules, and rebuild with "npm" it works

strangely, if you try to `yarn add frames.js` it looks like the library wasn't already installed, but adding it still doesn't resolve the issue

think you found the solution, but yeah monorepo weirdness. You gotta copy the folder out. May move the repo out of the folder

I had that problem earlier. To solve: I git cloned frames.js to a fresh directory, cd frames.js, then I added “node-gyp-build”:”^4.7.1” to package.json devdependencies, then npm install (I was having problems with hyp-build 4.8.0).  Then go into examples/frames js-starter and npm install