fix: nest deps chunk cannot be loaded when optimizing deps in build mode #13935
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
fixes #13933
Align the
load
logic ofoptimizedDepsBuildPlugin
withoptimizedDepsPlugin
. After loading the file from the cache, throw an exception if an error is encountered.Additional context
As mentioned in the last context I provided in the issue. I noticed that the
file
field for thechunks
in the.vite/deps/_metadata.json
is processed withflattenId
. But the chunk files generated by esbuild on the disk do not undergo theflattenId
process. Is this behavior expected? If it's necessary to flatten the chunk filenames, would it be better to flatten the filenames when generating the chunk files with esbuild? However, at the moment, I'm not sure how to flatten the generated chunks.What is the purpose of this pull request?
Before submitting the PR, please make sure you do the following
fixes #123
).