Bare imports should always be executed first

[arcanis]

Consider the following code:

import './polyfill';
import {foo} from './user-lib';

foo();

Esbuild inlines ./polyfill, causing the file to turn into:

import {
  foo
} from "./chunk-EN3LV7DE.js";

// polyfill.js
Object.somePolyfilledFunction = () => {
};

// main.js
foo();

This is invalid, as it means that the polyfill won't be available inside chunk-EN3LV7DE, causing the output to crash.

Esbuild should at least assume that the bare import, having no imported symbols, must have a significance in terms of side-effects and ensure that it gets evaluated at the right time.

[hyrious]

#399

Note that this problem also exists in Rollup.

[arcanis]

I checked #399 but since it mentioned multiple entry points I wasn't sure if this was a different issue or not 🤔

[hanayashiki]

seems you can't specify the order of execution of ecma modules per spec

[hanayashiki]

you can keep your polyfill while delay the run ofpiece of code that depends on it (e.g. lazy evaluation)

[arcanis]

Yes, that's what I currently do, but it's not ideal: the browser has to finish executing polyfills before even starting to fetch the actual application. It adds a small delay and indirection; I'm a little worried a browser will eventually show a white flash on reload if the delay is long enough.