fix: Do not attempt to use l10n files as sources for combined js files #38237
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.
My personal instance turned out an empty page after upgrading to 27.0.0-beta.2 and the log showed the trace below.
It seems that #38207 caused that translation json files were considered sources for the js combiner and its structure of course doesn't match the expected one as no file path is listed in there.
Iirc we don't use the combiner if debug mode is enabled so this might be the reason why this hasn't shown during development.