You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Next.js 13 has just come out, and brings with it various changes we'll need to support.
The use of react's use rather than getStaticProps or getServerSideProps. Among other things, this seems to mean that data fetchers will no longer have set names we can look for. 🎺
Layouts and component-level data fetching. Will pages still be the main unit of traceable code?
Streaming. No idea what effect this will have, if any.
Turbopack. The entire SDK is reliant on webpack for inserting code in the relevant places. For now turbopack is in alpha, is opt-in, and only works in dev, so this doesn't need to be solved immediately, but in the long run we will likely have to adapt all of our config code to work with both webpack and turbopack.
Next 13 has just been released, and it includes new features we don't yet support. This adds a note saying so to the top of our nextjs docs.
Issue tracking support in the SDK: getsentry/sentry-javascript#6056
Problem Statement
Next.js 13 has just come out, and brings with it various changes we'll need to support.
use
rather thangetStaticProps
orgetServerSideProps
. Among other things, this seems to mean that data fetchers will no longer have set names we can look for. 🎺Docs PR telling people that new features aren't yet supported: getsentry/sentry-docs#5694
#6290
The text was updated successfully, but these errors were encountered: