feat: batch original stack frame requests in turbopack overlay#75556
Closed
gaojude wants to merge 1 commit into02-01-works_for_webpackfrom
Closed
feat: batch original stack frame requests in turbopack overlay#75556gaojude wants to merge 1 commit into02-01-works_for_webpackfrom
gaojude wants to merge 1 commit into02-01-works_for_webpackfrom
Conversation
This was referenced Feb 1, 2025
Contributor
Author
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What?
Implements batch processing of stack frames in the development overlay middleware for Turbopack. Instead of processing frames individually, multiple frames can now be processed in parallel through a new POST endpoint.
Why?
This change improves performance when handling multiple stack frames by processing them concurrently rather than requiring separate requests for each frame.
How?
/__nextjs_original-stack-framesPOST endpointparseFilehelper to handle file path parsingcreateStackFramesfunction to process multiple framesPromise.allSettledFixes #[issue number]