Repository navigation
NextJs 15.3 shows warning after adding Sentry #16091
Description
Is there an existing issue for this?
- I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
- I have reviewed the documentation https://docs.sentry.io/
- I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases
How do you use Sentry?
Sentry Saas (sentry.io)
Which SDK are you using?
@sentry/nextjs
SDK Version
9.13
Framework Version
15.3
Link to Sentry event
No response
Reproduction Example/SDK Setup
No response
Steps to Reproduce
- Install NextJs 15.3
- Add Sentry using the wizard
- Run
npm run dev - See the following warning
Expected Result
No warning or a better way to understand that this warning comes in combination with Sentry. Since this is a NextJs warning I started to look into the turbopack configuration..
Actual Result
next dev --turbopack
▲ Next.js 15.3.0 (Turbopack)
- Local: http://localhost:3000
- Network: http://192.168.215.4:3000
- Experiments (use with caution):
· clientTraceMetadata
✓ Starting...
✓ Compiled instrumentation Node.js in 379ms
✓ Compiled instrumentation Edge in 134ms
✓ Ready in 1210ms
++ ⚠ Webpack is configured while Turbopack is not, which may cause problems.
++ ⚠ See instructions if you need to configure Turbopack:
https://nextjs.org/docs/app/api-reference/next-config-js/turboReacted by Sid Shaytay, Amol Bhave, Marc, Tomás Escobar and Greg Auger
Reacted by Lukas Stracke, Marc, Greg Auger, Nicholas Buckeridge and Daniel Williams
Metadata
Metadata
Assignees
Projects
- Status
Activity
lforst commentedon Apr 17, 2025
This is known but you can safely ignore it. Next.js emits this warning because the Sentry SDK defines a webpack callback field and when you run with turbopack Next.js warns you in case it is critical for your app to run the webpack callback.
lforst commentedon Apr 17, 2025
We can potentially fix this in the future when we only support Next.js versions that set the
process.env.TURBOPACKenv var when turbopack is used. Right now we need to unconditionally add the webpack callback because we cannot reliably detect turbopack due to old versions.Maybe we can also add some flag to the SDK that will skip over adding this field.
franzwilhelm commentedon Jun 5, 2025
+1 on this. Your solution sounds good @lforst
4 remaining items
csulit commentedon Jun 27, 2025
Any update on this?
RulaKhaled commentedon Jun 27, 2025
Not yet. I'll assign this and see what we can do
seanparkross commentedon Jul 12, 2025
+1
github-actions commentedon Jul 15, 2025
A PR closing this issue has just been released 🚀
This issue was referenced by PR #17013, which was included in the 9.39.0 release.
seanparkross commentedon Jul 31, 2025
🕺