You can upload any number of standard development files:
3D, WASM files, JavaScript files, JavaScript modules, etc, etc
for standard modern websites that one might source directly from the *file* not the *design* manager for varied reasons. This is also an issue in the local development server since the restricted file types by the CLI is WAY too strict. I don’t know what your backend looks like, but I know what the backends I’ve setup look like in my day - which is usually a one line config to fix this in the server conf. In which case, this is just lazy engineering.
Example: In NGINX it’s literally one line in /etc/nginx/mime.types. You just add:
application/javascript js mjs
Example for the bad behavior for MODULES:
Upload any JavaScript module (.js, .mjs). Link it <script type=“module” src=“URL.js/.mjs”> and this will fail because of module’s strict mime type checking per RFC standards and the `text/plain` Content-Type returned via the server file manager. Likewise, renaming to .mjs will cause `application/octet-stream` which is also wrong. The correct mimetype is “application/javascript” … Which isn’t returned because the server conf probably isn’t set up …
You can fix this hackily - but it’s wrong in terms of standards:
You can link via a standard tag <script src=“*.js/.mjs”> fine and it will aprse and work due to the lack of strict RFC standards. However, this is not correct and it prevents developers from providing module vs no module fallbacks per iOS and other standard patterns for legacy support.
On the same note … You completely sunsetted the legacy files API (which was infinitely better) and redirected every prior cache to a 301 and remove it from the wayback so nobody can even view the historical documentation anymore where you could fix mimetypes (although I don’t know if it would have fixed the render per it being completely removed).
Please stop removing things in the name of improvement.
Irrespective of your opinion on this, the fact is that you have a file server setup that doesn’t properly serve files … becuase it doesn’t serve proper content-type headers … the entire point of a file server …
That’s clearly not good efficacy.
This is the ONLY platform that consistently and routinely causes an inexplicable wrench in development efficacy precisely for the prior reason