Incorrect evaluation order with code splitting and dynamic imports

[amireh]

Consider the following code:

// index.js
import './a.js'
import './b.js'
import('./b.js')

// a.js
import './core-module.js'

// b.js
import './core-module.js'

I would expect core-module to be evaluated first, then a and then b, but in fact it appears that b is being evaluated before a. This is contrary to what other environments produce:

esbuild-splitting-test$ ./test.sh 
node:
[ 'core', 'a', 'b' ]
webpack:
[ 'core', 'a', 'b' ]
rollup:
[ 'core', 'a', 'b' ]
esbuild:
[ 'core', 'b', 'a' ]

Please see this repository to reproduce: https:/amireh/esbuild-splitting-test. The example index.js in this reduced form may look silly, but it does represent the case I'm facing in a large codebase where an entrypoint dynamically imports another file c that then imports b and causes incomprehensible issues.

This might be related to #399 only that this doesn't have to do with multiple entry points (or does it?)

Thank you for your terrific work.

[evanw]

Yes, I believe this is another instance of #399. When code splitting is active, dynamic import() creates another entry point for the imported file which is why the output file contains both index.js and b-[hash].js.

[amireh]

Ok that makes sense. I will close this one in favor of #399 then, thank you for clarifying.

Did I understand correctly from that thread that you are in the middle of addressing this, or are you open for a contribution? I'm willing to try as this is the last step for us to take esbuild to production.