Opened 3 years ago
Last modified 12 months ago
#33353 closed Bug
Can't collect static files if don't have vendor's Javascript source map files — at Initial Version
| Reported by: | Michael | Owned by: | nobody |
|---|---|---|---|
| Component: | contrib.staticfiles | Version: | 4.0 |
| Severity: | Release blocker | Keywords: | manifeststatic storage |
| Cc: | Adam Johnson | Triage Stage: | Unreviewed |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
If one is using 3rd party JavaScript library, its often a minified Javascript file, that quite likely it has a source map url in a comment at the end. However its very likely that one does not have this source map files for the vendor libraries (probably only the vendor uses them).
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.
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.
I would recommend if its a sourcemap, not even printing a warning. For the CSS files it could be worth printing a warning.