[turbopack] standardize chunk entry names for webpack and postcss loaders#94256
Open
lukesandberg wants to merge 2 commits into
Open
[turbopack] standardize chunk entry names for webpack and postcss loaders#94256lukesandberg wants to merge 2 commits into
lukesandberg wants to merge 2 commits into
Conversation
Contributor
Author
This stack of pull requests is managed by Graphite. Learn more about stacking. |
Contributor
Stats skippedCommit: b157db5 |
Contributor
Failing test suitesCommit: b157db5 | About building and testing Next.js
Expand output● instant-navigation-testing-api › renders runtime-prefetched content instantly during navigation |
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 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.

What?
Use the
chunk_pathapi for computing entrypoint filepath names for our node worker pool files. For postcss loaders ensure that the config filepath is part of the module ident of the transformer.Why?
I was investigating a bug in reported in next 16.2.6 (https://vercel.slack.com/archives/C09GRCW5MQR/p1780088728756579) and noticed that the chunk entry path construction logic was unusual. It happens to be that #91338 fixed the reported bug (just not released yet). This migrates all entry construction to the standard form