The bizarre part is that we find , , and that are non-edge functions, except the Vercel CLI does not list them as routes that it has generated a function for. When Vercel builds an application, it produces a series of serverless/edge functions, and static assets. We read those functions from the file system, and process them, so that they can be used for routing.
The files that it generates under are, in my experience, functions for pages + middleware. Now, yours appears to be generating 3 functions that have no corresponding routes. This means that at some point, something is being built that most likely shouldn't.
It is possible that this might be an edge case that we need to account for and add some custom logic to to deal with. It's also possible that it could be an issue with how your project is structured.
It is incredibly hard for us to try and debug this issue, identify a cause, or a solution without some kind of reproduction, so I'm afraid there isn't much help that can be provided otherwise.
