Emoji literals cause Next.js v14 HMR to crash when Sentry v8 server-side instrumentation is running

[staticshock]

I know that this appears to be Next.js-side error, but it baffles me that it did not happen until I updated Sentry to v8, even though I was previously using OTel w/Next.js. I don't have the setup to troubleshoot it deeply enough to file an appropriate Next.js issue. Sentry's OTel instrumentation is implicated here somehow, but I can't tell how.

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

8.50

Framework Version

Next v14.2.23

Link to Sentry event

No response

Reproduction Example/SDK Setup

Clone this sample repo and follow instructions in the README: https://github.com/staticshock/repros/tree/nextjs-14-sentry-8-15101

Otherwise, follow the longer instructions below.

Steps to Reproduce

1. Create a repo with Next.js 14 + Sentry v8 (or clone the sample repo I shared above)
2. Set up server-side Sentry tracking using instrumentation.ts (already done in the sample repo)
3. Add 'use client' to app/page.tsx
4. Run pnpm install && pnpm dev --turbo
5. Open app in browser (https://localhost:3000/)
6. Add an emoji character to the react component in app/page.tsx
7. Watch in disbelief as the app crashes and burns.

Expected Result

HMR does not break.

Actual Result

HMR breaks and stays broken until the dev server is killed and restarted.

[staticshock]

This issue relates to nextjs, not nestjs. I made a typo originally, and sadly I can't correct the wrong issue label.

[andreiborza]

Hey @staticshock, thanks for filing this.

We don't officially support Trubopack yet, you can follow the status by subscribing to #8105.

I couldn't really find the underlying cause from a quick look. The moment the next config is wrapped with withSentryConfig it starts occurring.

I recommend switching to non Turbopack builds and dev mode.

[staticshock]

Can be fixed by turning off turbopack or upgrading to Next v15.