Enable production source maps for index.js, fix CSS sourcemaps (#27291) #27295
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.
Backport #27291 by @silverwind
Previously, the production build never output sourcemaps. Now we emit one file for
index.js
because it is the most likely one where we need to be able to better debug reported issues like #27213. This will currently increase the binary size of gitea by around 700kB which is what the gzipped source map file has.Also, I fixed the CSS sourcemap generation which was broken since the introduction of lightningcss.
The chinese docs are machine-translated, please correct accordingly.