fix: don't generate report.html file for RC and Production #3125
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 are the relevant tickets?
#5265
Description (What does it do?)
This PR ensures that the report.html file generated by Webpack Bundle Analyzer is not served publicly in RC and Production environments. The file will now only be generated when the WEBPACK_ANALYZE environment variable is explicitly set to True during local development.
Screenshots (if appropriate):
How can this be tested?
Local Testing:
WEBPACK_ANALYZE=True
in your.env
file to confirm that the report.html file is generated.node node_modules/webpack/bin/webpack.js --config webpack.config.prod.js --bail
/static/bundles/
.Local Testing Without Analysis:
WEBPACK_ANALYZE
unset, and confirm that the report.html file is not generated by running the same command as above.RC/Production Testing:
Additional Context