DEV Community

Discussion on: Next.js 16 Broke My App in 4 Places and None of Them Threw an Error

Collapse
 
leob profile image
leob

"Next.js 16 replaced middleware.ts with proxy.ts" - I mean, why ... ? Seems a totally unnecessary change, only to annoy the user? On top of that, I can't imagine proxy.ts to be a "better" name than middleware.ts ...

However - doesn't Next.js document its upgrades? As in, a CHANGELOG document or an upgrade guide?

Collapse
 
shubhradev profile image
Shubhra Pokhariya

Haha yeah fair point, proxy.ts does feel a bit odd especially when middleware.ts already made sense so the rename caught me off guard too.

From what i understood the idea is it handles more than just middleware now, closer to a full request proxy layer, but still agree the silent failure with zero warning is the jarring part.

And yeah they do have docs and a changelog, the codemod handles most of it but partial upgrades or missed files is where stuff like this sneaks through.