Changes between Initial Version and Version 6 of Ticket #33353
- Timestamp:
- Jan 6, 2022, 8:38:53 AM (3 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #33353
- Property Type Uncategorized → Bug
- Property Cc added
- Property Summary Can't collect static files if don't have vendor's Javascript source map files → Can't collect static files if don't have vendor's JavaScript source map files
-
Ticket #33353 – Description
initial v6 3 3 Django version 4 introduces a new features of adjusting the URLs of these source map urls. Unfortunately if one does not have these source maps, its generates an error and stops. This seems unncessary that one can't create a release due to an unused third party file. 4 4 5 During storage post processes the files, if it can't file the file in the URL, please rather print a warning, or just skip replacing that url.5 Altohugh I think it should only print a warning, as dicussed below people feel its worthwhile to keep this breaking change that breaks third part packages. Can we at least make it only raise an error if `settings.DEBUG == True`. That way in production where the sourcemaps are used less, its okay. 6 6 7 I would recommend if its a sourcemap, not even printing a warning. For the CSS files it could be worth printing a warning. 7 Alternatively/Additionally, could there be a `settings.SOURCEMAPE_EXCEPTION` etc that allows one to turn off this new break change?