Top level await for import() function stopped working in Chrome

[Antony92]

Describe the bug

For some reason when building for production and using top level await for an import() function that imports a module which imports another module the import() never completes with await. This started happening recently on Chrome (on Safari and Firefox it works fine) and this does not happen when running in dev mode. Not really sure if the issue is Chrome related or with vite bundle when running for production.

Here is a quick summary of the reproduce link:

We have a main.ts file with a top level await import for module1.ts

import './style.css';

const div = document.querySelector('div')!;

await import('./module1');

div.innerHTML = 'Finished...';

module1.ts includes an export of function that imports another module. In this case module2.ts

export const randomFunction = () => {
  import('./module2');
};

Now running this with stackblitz in dev mode npm run dev you should see "Finished" displayed on both Chrome and Safari.
Running npm build-prod and then npm run preview displays "Finished" in Safari, but in Chrome await import('./module1') never completes and you should see "Loading..."

Workaround is to use import('./module1').then(() => // code to be executed after module load) instead of await import('./module1');

Reproduction

https://stackblitz.com/edit/vitejs-vite-85uvzu?file=src%2Fmain.ts

Steps to reproduce

npm run build-prod
npm run preview

System Info

System:
    OS: macOS 15.0
    CPU: (12) arm64 Apple M3 Pro
    Memory: 1.43 GB / 18.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.16.0 - /usr/local/bin/node
    npm: 10.8.1 - /usr/local/bin/npm
  Browsers:
    Chrome: 129.0.6668.59
    Safari: 18.0
  npmPackages:
    vite: ~5.4.6 => 5.4.6

Used Package Manager

npm

Logs

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[stackblitz]

Start a new pull request in StackBlitz Codeflow.

• vitejs-vite-85uvzu (Open reproduction)

[bluwy]

From your system info, I think you're hitting a chrome bug:

• https://x.com/antfu7/status/1836846357489012816
• https://github.com/antfu/repro-chrome-v129

[JohnGreek]

I reproduced it in a fresh Vite (Vanilla) project. await import in dev mode works ok, build & preview is blank on v129.0.6668.59 Chromium-based browsers.

I also tested await import with React+Typescript+SWC (fresh project again) and it's the opposite. Dev mode shows empty screen and when built and previewed, it's working ok.

[Nettsentrisk]

Can confirm, a relatively simple app created with @vitejs/plugin-react-swc is now behaving this way, producing a blank page, in Chrome/Edge 129. Running the same app in Opera 113 works fine.

There's no use of await import in user code in this project, so I'm guessing some internal Vite use (or @vitejs/plugin-react-swc) is what's manifesting the issue.

Anything that can be done other than using another browser and waiting for an update to Chrome/Edge?

[jardenliu]

Can confirm, a relatively simple app created with @vitejs/plugin-react-swc is now behaving this way, producing a blank page, in Chrome/Edge 129. Running the same app in Opera 113 works fine.

There's no use of await import in user code in this project, so I'm guessing some internal Vite use (or @vitejs/plugin-react-swc) is what's manifesting the issue.

Anything that can be done other than using another browser and waiting for an update to Chrome/Edge?

try vite-plugin-top-level-await?

[jefflundberg]

This seems to be related to a Chromium bug.

Reproduction of the bug

It's fixed in Chrome 130 available via the Canary nightly build or Microsoft Edge Canary and Dev Channel Builds.

[SkyWalker653]

I am using vite-plugin-top-level-await plugin as a temporary workaround.

[NickdeK]

@SkyWalker653 This has done the trick for us, thanks for sharing, much appreciated!
Spoke to soon, it did not work...

It eventually did work but we loaded the plugin to late and in the wrong place. We are using Quasar with boot files and we had to add it to the vitePlugins in the quasar config to make this work.

[Nettsentrisk]

Problem seems to be gone for me in Edge 130.

[sapphi-red]

Closing as this seems to be fixed in chromium 130 and chrome/edge 130 has been released.