NextJS Logging bug, all logs show up in colocated [someId].js function

[joe.roddy]

Hi, just ran into a really annoying bug that made me waste like 6 hours.

For some reason, if you have two colocated api files:

/api
   /files
     /[fileId].ts
     /upload.ts

upload.ts’s logs will show up in the function logs for [fileId].ts. Was really annoying trying to figure out why none of my logs were showing up.

[hillary]

Hey there, @joe.roddy

Sorry to hear you encountered an obstacle. Could you share your site and function log where you found this so that I can loop in the appropriate team? Thanks.

[joe.roddy]

Netlify site: bt-platform.netlify.app

Function where all colocated logs are printed:
Function _api_content_contentId-PARAM_files_fileId-PARAM-handler

Function where it should have been printed:
Function _api_content_contentId-PARAM_files_upload-handler

[joe.roddy]

@hillary Another bug I just found:

NextJs API - cannot find module 'formidable' - works locally

Netlify site: https://bt-platform.netlify.app/ We have a Nextjs API that accepts a file in the body and parses it via formidable (which is in our package.json). Everything is working great locally. Here’s the api code: import formidable, { File } from 'formidable'; //^ throws error import type { NextApiRequest, NextApiResponse } from 'next'; export const config = { api: { bodyParser: false } }; export default async function handler(req: NextApiRequest, res: NextApiResponse<any>) { conso…

Not sure when this was rolled about, but recently NextJs api endpoints started to be sharded into separate cloud functions for each endpoint. Previously they were all handled by one cloud function.

The code in the linked issue only fails when deployed via the sharded apis, but when it’s deployed as a bundled set of apis to __netlify-handler it works. Still unclear as to why some deploys use one method over the other (sharded vs bundled functions).

[hrishikesh]

NextJs API - cannot find module 'formidable' - works locally

Hey @joe.roddy, With the release of v4.28.4 of Next.js Runtime, we’ve reverted the change of switching to individual function for each API route. This should solve the problem you’re seeing here as well as in the other thread. Let us know if it works.