Bug [Next.js 16]: Vercel console warning about middleware missing

Feedback
1

Hi! I recently upgraded to Next.js 16, and I’ve already run the codemod to migrate middleware.ts to proxy.ts as described here: Renaming Middleware to Proxy | Next.js

However, I’m getting the following warning when deploying:

WARNING: Unable to find source file for page middleware with extensions: tsx, ts, jsx, js, this can cause functions config from vercel.json to not be applied

I’m assuming this is a minor display thing and not actually an issue but wanted to confirm anyways. Thanks in advance!

4

I have the same problem and haven’t found a solution yet.

5

I also facing same issues. What you meaning about this reply?

6

You can safely ignore this warning, it’s a false positive for some code looking for a middleware.ts file and not recognizing proxy.ts as a valid alternative

There is an active PR to fix this

7

Thank you so much for your patience while we worked on this. We wanted to let you know that we have just published a new version of the Vercel CLI on our build infrastructure. With this update, you should no longer see warnings about legacy middleware.ts when using Proxy files on Next.js v16+.

Please feel free to test it out, and let us know if you encounter any further issues. We’re here to help!

8

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.