esbuild bundle=true causing unplugin-auto-import invalid

[cest-la-v]

Hi, I've just start using quasar to build browser extensions, when I'm trying to reuse codes between src-bex/background.ts and src, I found out that the modules auto imported by unplugin-auto-import won't be available in the built output dist/backgroud.js.

I see you are using bundle: true to inline all the modules needed by background/content/dom script and bundle them into single outputs.

I've extended esbuild config like this:

      extendBexScriptsConf(esbuildConf) {
        esbuildConf.plugins = [
          ...esbuildConf.plugins,
          AutoImportForEsbuild({
            imports: ['vue', 'vue-router', 'vue-i18n', '@vueuse/core', 'quasar'],
            dirs: [
              'src/composables', // only root modules
              // './composables/**', // all nested modules
              'src/stores',
            ],
            dts: 'src-bex/auto-import.d.ts',
          }),
        ];
        console.log('esbuildConf: ', esbuildConf);
      },

Yet, the modules supposed to be auto imported still won't be inlined into the output files.

I'm guessing this is caused by the bundle=true feature can only inline the imports analyzable at compile-time but not runtime (https://esbuild.github.io/api/#non-analyzable-imports), while the auto imported modules are actually analyzable until runtime (dynamic imports?). Thus, esbuild in bundle mode does not support unplugin-auto-import?

It is a bit hideous to collect all the shared code in one special place and only able to use manual import on them in the bex scripts.
Are you planning on to use Vite to build background/content/dom script as well as the BEX UI itself, instead of using an extra build tool esbuild? I think Vite also support building bundled single script file like this vitejs/vite#2739.