A place for developers to talk about building on Farcaster.

/dev

does anyone have a good connection at vercel? 

we keep running a “too many files” error when trying to visit any route with server-side rendering on deployment. 

local builds run just fine.

did you figure this out? had run into similar issues a while ago and might be able to help

clanking professionally | bc skier | surfer | baker

nice! can dm too but top of mind

nextjs specific
- if you’re below v15, upgrade to 15. there are some module resolution improvements on by default (plus more sensible caching). I think app router may also help with this
- checkout ‘optimizePackageImports’ if you’re using a barrel-like file (often icons) or some library not on that list it may be the culprit
- using the bundle analyzer locally may help, if you see anything large being imported that’s unexpected

various
- trying to keep file dependencies in a tree-like structure. Npm modules don’t matter here, but spaghetti imports can really balloon built code by transitively importing UI or test code to server logic
- introducing DI-like patterns/avoiding global instantiating. tree-shaking has gotten pretty smart, but most anything being run at the global level in a file will run on import even if it’s ultimately not used
- updating the node version to vercel’s latest supported (22 now I think) may also help module resolution

we’re in touch with their team but if you’ve figured it out and have tips! That would be awesome. 

@parker