Next.js/Vercel Feature compatibility table

[lforst]

We have some issues in the Next.js SDK that may have originated from our auto-wrapping approach. The following table outlines which Sentry SDK features and which Next.js features work and/or have issues, off and on Vercel for different versions of Next.js.

Feature	10	10 (Vercel)	11	11 (Vercel)	12	12 (Vercel)	13	13 (Vercel)
Auto-wrapping errors	✅	✅	✅	✅	✅	✅	✅	✅
Pageload-Transactions	✅	✅	✅	✅	✅	✅	✅	✅
Navigation-Transactions	✅	✅	✅	✅	✅	✅	✅	✅
Middleware	N/A	N/A	N/A	N/A	✅	✅	✅	✅
Dev mode	✅	N/A	✅	N/A	✅	N/A	✅	N/A
Experimantal edge API routes	N/A	N/A	N/A	N/A	✅	✅	✅	✅

Takeaways

• We should fix error reporting in our wrappers on Vercel (Errors aren't being reported in Next.js data-fetching methods on Vercel #6117)
• We should fix NFT (https://github.com/vercel/nft) (@sentry/nextjs 7.15 and 7.16 have issues with @vercel/nft #5998, Resolving files with querystring vercel/nft#319) (fixed in fix(resolution): Fix resolution of querystringed imports in ESM files vercel/nft#322)
• Webpack 4 source maps are broken (Sourcemaps are broken on Next.js + Webpack 4 when auto wrapping instrumentation is enabled #6118)
• We should provide users with a way to opt out of SDK initialization on routes that run on the Vercel Edge runtime (Provide Next.js SDK users with a way to opt out certain routes to use different runtimes #6119)
• We should make the Next.js SDK isomorphic to get rid of "not exported" warnings

[lforst]

Everything in the table should work with the 7.31.0 release of the SDK.