When discovering Vercel Functions from a project in a monorepo, the filePathMap parameter may reference files out of the bounds of the current project.
This is currently only observed in Next.js projects. The Vercel Build Output API documentation does not reference this parameter at all, so it is likely this issue only happens with Next.js.
Due to the missing documentation, it is hard to quantify how to properly implement filePathMap. We likely need to root the deployment package at the actual repository root, which needs to be discovered somehow. At the same time, the project root needs to be defined as a parameter, and only relevant files should be included to avoid the deployment package becoming too big.
This issue is currently blocking full Next.js compatibility.
When discovering Vercel Functions from a project in a monorepo, the filePathMap parameter may reference files out of the bounds of the current project.
This is currently only observed in Next.js projects. The Vercel Build Output API documentation does not reference this parameter at all, so it is likely this issue only happens with Next.js.
Due to the missing documentation, it is hard to quantify how to properly implement filePathMap. We likely need to root the deployment package at the actual repository root, which needs to be discovered somehow. At the same time, the project root needs to be defined as a parameter, and only relevant files should be included to avoid the deployment package becoming too big.
This issue is currently blocking full Next.js compatibility.