ES6 module fails on Safari mobile (iOS14.6)

I’m experimenting with Javascript modules both via desktop (latest Chrome) and mobile (Safari with iOS 14.6) and my code works perfectly on the desktop (standard browser or mobile emulation mode) but fails on my iPhone. The imported JS code using <script type="module"> simply doesn’t execute despite being supported since Safari iOS 11 onward according to

The test code below, adapted from How to serve ES6 modules on Safari? , is hosted on a webserver in my local network reachable by both the mobile & desktop clients. For mobile debugging I’m using a locally copied version of to render console.log commands on mobile.


  <meta name="viewport" content="width=device-width, initial-scale=1.0">
      console.log("Start of test_ios.html...");
    <title>TESTS IOS</title>
    <script src="/static/hnl.mobileConsole.1.3.js"></script>
    <script nomodule src="/static/fallback.js"></script>
    <script type="module">
        console.log("Starting the main script.");
        // The following line seems to cause an error in Safari only
        import { TestClass } from './static/test_module.js';
        // The rest is not executed due to the error
        let test_class = new TestClass;
        console.log("End of test_ios.html...");


export class TestClass {
    constructor() {
      console.log("Created a test class in test_module.js");



Result on the desktop, as expected

Test string test_module.js gets written onto the web page & the following lines are in the console:

--==## Mobile Console v1.3.5 active ##==--
End of test_ios.html...
Starting the main script.
Created a test class in test_module.js

Result on iOS 14 – neither the module JS nor the fallback get executed

The page is blank (no document.body.append(...) was executed) & only the following lines are in the console:

--==## Mobile Console v1.3.5 active ##==--
End of test_ios.html...

Further checks already done:

  1. I sniffed the network and I see that /static/test_module.js is requested by the mobile device (no request for fallback.js).
  2. The content-type of /static/test_module.js returned by the webserver seems coherent (application/javascript; charset=utf-8).
  3. Renaming test_module.js to test_module.mjs doesn’t help (same outcome as above)

Source: Ask Javascript Questions