Skip to content

feat(nextjs): Bump minimum required Next.js version to 13.2.0#11097

Merged
lforst merged 20 commits intodevelopfrom
lforst-min-nextjs-version
Mar 15, 2024
Merged

feat(nextjs): Bump minimum required Next.js version to 13.2.0#11097
lforst merged 20 commits intodevelopfrom
lforst-min-nextjs-version

Conversation

@lforst
Copy link
Copy Markdown
Contributor

@lforst lforst commented Mar 14, 2024

Ref #9838

Bumps the next peer dependency to 13.2.0 and removes integration tests that test versions below that version.

@lforst lforst requested review from AbhiPrasad and mydea March 14, 2024 12:27
@lforst lforst marked this pull request as ready for review March 14, 2024 12:27
Copy link
Copy Markdown
Contributor

@AbhiPrasad AbhiPrasad left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can remove Node 14 from the matrix now -

node: [14, 16, 18, 20, 21]

},
"peerDependencies": {
"next": "^10.0.8 || ^11.0 || ^12.0 || ^13.0 || ^14.0",
"next": "^13.2.0 || ^14.0",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IMO we should make this 14.1.3 for vercel/next.js#61194

Suggested change
"next": "^13.2.0 || ^14.0",
"next": "^13.2.0 || ^14.1.3",

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't understand how that would be useful. Can you elaborate? We still have to maintain anything pre 14.1.3.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well if we make 14.1.3 the minimum for v14, we don't have to maintain anything pre 14.1.3. It incentivizes people to use the framework version that works best for the SDK, but I can also see how it introduces friction.

@lforst lforst enabled auto-merge (squash) March 14, 2024 15:37
@lforst lforst force-pushed the lforst-min-nextjs-version branch from 4b01add to a0be4c7 Compare March 15, 2024 09:26
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Mar 15, 2024

size-limit report 📦

Path Size
@sentry/browser (incl. Tracing, Replay, Feedback) 82.98 KB (added)
@sentry/browser (incl. Tracing, Replay) 78.5 KB (added)
@sentry/browser (incl. Tracing, Replay with Canvas) 81.82 KB (added)
@sentry/browser (incl. Tracing, Replay) - with treeshaking flags 72.09 KB (added)
@sentry/browser (incl. Tracing) 78.5 KB (added)
@sentry/browser (incl. browserTracingIntegration) 78.5 KB (added)
@sentry/browser (incl. feedbackIntegration) 76.45 KB (added)
@sentry/browser (incl. feedbackModalIntegration) 76.64 KB (added)
@sentry/browser (incl. feedbackScreenshotIntegration) 76.65 KB (added)
@sentry/browser (incl. sendFeedback) 72.52 KB (added)
@sentry/browser 71.95 KB (added)
CDN Bundle (incl. Tracing, Replay, Feedback) 76.62 KB (added)
CDN Bundle (incl. Tracing, Replay) 71.48 KB (added)
CDN Bundle (incl. Tracing) 37.82 KB (added)
CDN Bundle 25.68 KB (added)
CDN Bundle (incl. Tracing, Replay) - uncompressed 224.12 KB (added)
CDN Bundle (incl. Tracing) - uncompressed 114.06 KB (added)
CDN Bundle - uncompressed 75.9 KB (added)
@sentry/react (incl. Tracing, Replay) 80.46 KB (added)
@sentry/react 73.93 KB (added)

@lforst lforst merged commit 1acf54f into develop Mar 15, 2024
@lforst lforst deleted the lforst-min-nextjs-version branch March 15, 2024 10:50
cadesalaberry pushed a commit to cadesalaberry/sentry-javascript that referenced this pull request Apr 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants