Raf
I just want to add to this, that I ran into a similar issue whereupon deployment I receive invariant 138 saying "Maximum depth exceeded", and disabling swcMinify solves the issue...
@kdy1 I just tested a deployment with [12.1.7-canary.16](https://www.npmjs.com/package/next/v/12.1.7-canary.16) and it threw the same issue. The repo is private, but if you need anything specific let me know!
> @wguerram Do you have a public repo with this configuration? When I build it using your method I'm unable to zip the correct artifact size. For me it should...
Just me then. Your serverless method is also way better @estyh!! Odd it seems I'm the only one who can't deploy a proper build.
So is Serverless versions >=3 messed up for Next deployments? I use Aws Amplify to deploy and I hijack the serverless config with my own, it seems that deploying a...
I'm just modified my config to use 2.72.2 so I'll see if it builds, I wonder if this has been the issue the whole time! I could never deploy with...
Are you referring to VS_OSS?
@mswezey23 So there's going to be a beta of the new build system at some point in the near future (it's been up in the air atm, check the Next...
Stephen brought this up in the Amplify Office Hours. NextJS 12 introduced middleware and server components. In the middleware demo when using Vercel you can use req.geo to resolve the...
@ferdingler Correct, I would like to be able to use the Lat & Lon headers as well as the other location-specific headers. At the moment I run the user's IP...