⌘K
Jacob Paris How are you injecting the cookie? Can you add it in a request interceptor instead so it resolves at request time instead of ahead of time?
Bharathrnair7 1528 async function processQueue(newAccessToken?: string, error?: any) { while (requestQueue.length) { const queued = requestQueue.shift(); if (!queued) continue; if (error) { queued.reject(error); } else { try { // Explicitly set the new token on the queued request config // instead of relying on the interceptor (which reads stale cookies) if (newAccessToken) { queued.config.headers = { ...queued.config.headers, Authorization: \Bearer ${newAccessToken}\, }; } const response = await http(queued.config); queued.resolve(response); } catch (err) { queued.reject(err); } } } } try { const newAccessToken
Pauline P. Narvas It sounds like there is no Next.js version in your package.json file. Can you check for this? "next": "15.0.2" How did you do this? 🙂
Ryu Hi, That error usually means Vercel cannot find the package.json that contains next, or the project root is set incorrectly. A few things to check: In your repo, confirm next is listed in dependencies or devDependencies in the same package.json Vercel is building from. In Vercel, open Project Settings -> General -> Root Directory and make sure it points to the folder that contains that package.json. If this is a monorepo, set the root directory to the actual app folder, for example apps/web. Make sure the repo includes the lockfile from the same package manager you are using. Redeploy after ch
Pauline P. Narvas Spot on! Your assumption is exactly right. :D Since that Hero component with revalidate is shared across your generateStaticParams pages, each one of those 1,350+ pages effectively "inherits" its own ISR schedule. This means that after the 1-week window, a visit to any page will kick off a background regeneration. If your traffic hits all those pages, you're looking at a huge spike in serverless executions which is definitely why you're seeing those limits pop up! A couple ways we can optimize this: Fetch client-side: This is the most straightforward path. If you move the GitHub stars fetch to
Juan D. Martinez I was thinking of going client side or creating a dedicated landing page for this hero section. I'm not a big fan of client fetching on stuff that doesn't change often, but haven't thought of that API apporach you mentioned, guess I'll try that one instead. I appreciate the help @pawlean 🙌🏻
Pauline P. Narvas No worries, Juan! 😃 Come back with updates - excited to hear how you get on 🙂
