Jonah Allibone

@dphang what is the default target used by this package when you deploy? I was under the impression (I think now wrongly) that it was the old serverless target, with...

@dphang honestly the documentation I've seen from Vercel on this front has been incredibly confusing. Sometimes it seems like `serverless` is going away and `serverless-trace` is [staying](https://github.com/vercel/next.js/issues/20487). In that comment...

@dphang not to blow up this thread, but I found a new useful things: 1. `target` itself is going away, not just the `serverless` or `experimental-serverless-trace` [here](https://nextjs.org/blog/next-12#output-file-tracing) > Bringing @vercel/nft...

@dphang they also added two exportable functions where you can ignore/add dependencies which might not be properly bundled

@hotlong Pretty sure this is because this doesn't support the new object rewrites from Next.js, per the note (Note that object format is not yet supported.) in the [README](https://github.com/serverless-nextjs/serverless-next.js)

Next.js only outputs the files required to run the application, and at this point, it's meant to be agnostic of deployment target. Whether it be docker, raw node, or Serverless,...

> I've learned some useful things in this thread, but unfortunately I don't think I'm much closer to an answer about [not] just using standard Next.js with APIGW proxy integration...

I'd be curious to know if it works. From that description I'm inclined to think they won't (I'm speaking specially of ones used in next.config.js) Also based on the issues...

@CloudDrivenSolutions This also fixed my issue in NextJS when using `next/dynamic` did not suffice. I don't know that it's the optimal solution but I will be using it for now....

+1 Same issue here. Only way to get my linter to pass is by deleting the lint cache before every run.