-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
deps(changelog): Bump Next.js to canary and Sentry SDK to latest #10876
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Bundle ReportChanges will increase total bundle size by 342.83kB ⬆️
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
shouldn't this be .env.example? 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I purposefully added this. You probably already know this but .env.development
will get picked up if you run next dev
which I hope will save people time and confusion when they try to run the dev server for the changelog for the first time.
@@ -21,15 +21,14 @@ | |||
"@radix-ui/react-icons": "^1.3.0", | |||
"@radix-ui/react-toolbar": "^1.0.4", | |||
"@radix-ui/themes": "^2.0.3", | |||
"@sentry/nextjs": "^8.8.0", | |||
"@spotlightjs/spotlight": "^2.1.1", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
q: Why did you remove spotlight?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It was one more thing I needed to get working with the new Next.js version. I will add it back in a follow-up. But good that you bring it up!
Bumps Next.js to a canary version so that we can test out newer Next.js features that are useful for instrumentation.
All the changes that look unrelated in this PR are actually things that started throwing errors in dev in the new version.