Skip to content

fix(nextjs): Inject Next.js version for dev symbolication #17379

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

Merged
merged 7 commits into from
Aug 12, 2025

Conversation

chargome
Copy link
Member

@chargome chargome commented Aug 11, 2025

Closes: #17369

We depended on next internals for getting the Next.js version at server runtime. I switched this to use our value injection loader as this works both reliably for webpack + turbopack.

Also, if for whatever reason we do not have a next version in the dev symblicator we return early as we don't know how to process the frames without it.

This derailed into a slight side-quest of refactoring the turbopack value injection, please don't hate me.

@chargome chargome self-assigned this Aug 11, 2025
Copy link

linear bot commented Aug 11, 2025

cursor[bot]

This comment was marked as outdated.

cursor[bot]

This comment was marked as outdated.

cursor[bot]

This comment was marked as outdated.

cursor[bot]

This comment was marked as outdated.

@chargome chargome enabled auto-merge (squash) August 12, 2025 13:20
@chargome chargome merged commit a0c04a7 into develop Aug 12, 2025
184 checks passed
@chargome chargome deleted the cg-fix-next-dev-symbolication-loop branch August 12, 2025 13:23
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.

Infinite loop with GET /__nextjs_original-stack-frame requests on Next.js dev mode
2 participants