Remove UnsupportedModule plugin #8439
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
8 Ignored Deployments
|
This stack of pull requests is managed by Graphite. Learn more about stacking. Join @wbinnssmith and the rest of your teammates on |
|
Logs
See job summary for details |
🟢 Turbopack Benchmark CI successful 🟢Thanks |
|
bgw
approved these changes
Jun 12, 2024
wbinnssmith
force-pushed
the
wbinnssmith/before-resolve-module
branch
from
71787a9 to
d23d385
Compare
wbinnssmith
force-pushed
the
wbinnssmith/rm-unsupported-plugin
branch
from
44c08a3 to
f681bdc
Compare
wbinnssmith
force-pushed
the
wbinnssmith/rm-unsupported-plugin
branch
from
f681bdc to
3c0f592
Compare
ForsakenHarmony
pushed a commit
to vercel/next.js
that referenced
this pull request
Jul 25, 2024
This change removes the UnsupportedModule issue module from the codebase. It was used by the UnsupportedModule resolve plugin in Next.js, but there are no longer any unsupported modules. This should improve performance as this check was performed during every resolution.
ForsakenHarmony
pushed a commit
to vercel/next.js
that referenced
this pull request
Jul 29, 2024
This change removes the UnsupportedModule issue module from the codebase. It was used by the UnsupportedModule resolve plugin in Next.js, but there are no longer any unsupported modules. This should improve performance as this check was performed during every resolution.
ForsakenHarmony
pushed a commit
to vercel/next.js
that referenced
this pull request
Jul 29, 2024
This change removes the UnsupportedModule issue module from the codebase. It was used by the UnsupportedModule resolve plugin in Next.js, but there are no longer any unsupported modules. This should improve performance as this check was performed during every resolution.
ForsakenHarmony
pushed a commit
to vercel/next.js
that referenced
this pull request
Aug 1, 2024
This change removes the UnsupportedModule issue module from the codebase. It was used by the UnsupportedModule resolve plugin in Next.js, but there are no longer any unsupported modules. This should improve performance as this check was performed during every resolution.
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.
This change removes the UnsupportedModule issue module from the codebase.
It was used by the UnsupportedModule resolve plugin in Next.js, but there are no longer any unsupported modules.
This should improve performance as this check was performed during every resolution.