-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Fix internal mjs/mts references as well #5458
Merged
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 ↗︎ 11 Ignored Deployments
|
✅ This change can build |
|
Linux Benchmark for 88fc2fcClick to view benchmark
|
sokra
approved these changes
Jul 4, 2023
MacOS Benchmark for 88fc2fc
Click to view full benchmark
|
kodiakhq bot
pushed a commit
to vercel/next.js
that referenced
this pull request
Jul 4, 2023
## Turbopack updates * vercel/turborepo#5457 * vercel/turborepo#5458
shuding
pushed a commit
to vercel/next.js
that referenced
this pull request
Jul 8, 2023
## Turbopack updates * vercel/turborepo#5457 * vercel/turborepo#5458
ForsakenHarmony
pushed a commit
to vercel/next.js
that referenced
this pull request
Jul 25, 2024
### Description In #5457, I fixed internal .jsx?/.tsx? references not being processed. However, it turns out we also use `.mjs` for structured images in Next.js, which also use internal references. ### Testing Instructions Next.js CI
ForsakenHarmony
pushed a commit
to vercel/next.js
that referenced
this pull request
Jul 29, 2024
### Description In #5457, I fixed internal .jsx?/.tsx? references not being processed. However, it turns out we also use `.mjs` for structured images in Next.js, which also use internal references. ### Testing Instructions Next.js CI
ForsakenHarmony
pushed a commit
to vercel/next.js
that referenced
this pull request
Aug 1, 2024
### Description In #5457, I fixed internal .jsx?/.tsx? references not being processed. However, it turns out we also use `.mjs` for structured images in Next.js, which also use internal references. ### Testing Instructions Next.js CI
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.
Description
In #5457, I fixed internal .jsx?/.tsx? references not being processed. However, it turns out we also use
.mjs
for structured images in Next.js, which also use internal references.Testing Instructions
Next.js CI