-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Turbopack HMR: Avoid infinite loops caused by cycles between modules in the dependency chain. #8210
Merged
Conversation
This file contains 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
…in the dependency chain. Previously, if a change were made in a module that participated in a dependency cycle, gathering affected modules would loop infinitely. This check prevents this. Test Plan: Fixes vercel/next.js#65537
The latest updates on your projects. Learn more about Vercel for Git ↗︎
7 Ignored Deployments
|
🟢 Turbopack Benchmark CI successful 🟢Thanks |
✅ This change can build |
|
…odules in the dependency chain.
bgw
approved these changes
May 24, 2024
timneutkens
approved these changes
May 28, 2024
ForsakenHarmony
pushed a commit
to vercel/next.js
that referenced
this pull request
Jul 25, 2024
…in the dependency chain. (vercel/turborepo#8210) Previously, if a change were made in a module that participated in a dependency cycle, gathering affected modules would loop infinitely. This check prevents this. Test Plan: Fixes #65537
ForsakenHarmony
pushed a commit
to vercel/next.js
that referenced
this pull request
Jul 29, 2024
…in the dependency chain. (vercel/turborepo#8210) Previously, if a change were made in a module that participated in a dependency cycle, gathering affected modules would loop infinitely. This check prevents this. Test Plan: Fixes #65537
ForsakenHarmony
pushed a commit
to vercel/next.js
that referenced
this pull request
Jul 29, 2024
…in the dependency chain. (vercel/turborepo#8210) Previously, if a change were made in a module that participated in a dependency cycle, gathering affected modules would loop infinitely. This check prevents this. Test Plan: Fixes #65537
ForsakenHarmony
pushed a commit
to vercel/next.js
that referenced
this pull request
Aug 1, 2024
…in the dependency chain. (vercel/turborepo#8210) Previously, if a change were made in a module that participated in a dependency cycle, gathering affected modules would loop infinitely. This check prevents this. Test Plan: Fixes #65537
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Previously, if a change were made in a module that participated in a dependency cycle, gathering affected modules would loop infinitely. This check prevents this.
Test Plan: Fixes vercel/next.js#65537