2 comments

[ 3.9 ms ] story [ 13.9 ms ] thread
I wonder if this is true of any framework on vercel, or if it’s specific to Next.js.

I ran into some opinionated engineering decisions while using it (particularly in regards to decisions around handling caching headers). I thought it was vercel at first, but it turned out to be framework-level.

This was just a bad regex. Just pushed a fix, should be live any minute.