Surprising output order of imported core-js

[danr]

Setup

main.ts:

import "core-js/features/array/flat-map"
import {thing} from "./import"

console.log(thing())

import.ts:

const x = [].flatMap(i => i)

export function thing() { return x }

Observed output

$ esbuild main.ts --bundle
[ ... ]
  // node_modules/core-js/es/array/flat-map.js
  var require_flat_map = __commonJS((exports, module) => {
    require_es_array_flat_map();
    require_es_array_unscopables_flat_map();
    var entryUnbind = require_entry_unbind();
    module.exports = entryUnbind("Array", "flatMap");
  });

  // node_modules/core-js/features/array/flat-map.js
  var require_flat_map2 = __commonJS((exports, module) => {
    var parent = require_flat_map();
    module.exports = parent;
  });

  // import.ts
  const x = [].flatMap((i) => i);
  function thing() {
    return x;
  }

  // main.ts
  const flat_map = __toModule(require_flat_map2());
  console.log(thing());
})();

We see that flatMap is called before the __toModule of core-js's flat-map.

Expected output

I am expecting to see the module to be instantiated before flatMap is called, like this:

$ esbuild main.ts --bundle
[ ... ]
  // main.ts
  const flat_map = __toModule(require_flat_map2());

  // import.ts
  const x = [].flatMap((i) => i);
  function thing() {
    return x;
  }

  // main.ts, continued
  console.log(thing());
})();

[evanw]

Thank you very much for reporting this issue. This is similar to #399 and comes from a misunderstanding I had about how ES6 import statements are ordered. I believe I have fixed this ordering issue in the latest release.

[danr]

I can confirm that 0.7.9 now makes the expected output :) Thank you!