Why does async + await return AsyncFunction?

Question

code

const config = async () => {
  return await import("../test");
}

console.log(config);

../test

export const config = {
  value1: 1,
  value1: 2,
};

I want config in ../test but this returns [AsyncFunction: config].

const config = await import("../test") will return what you want. async (...) => { ... } is literally the definition of an async function. — Amadan
– Amadan, Commented Jan 21, 2022 at 4:49

Alex Wayne · Accepted Answer · 2022-01-21 04:59:16Z

2

async () => {} is a function declaration. So you assigned config to a function.

You have to call that function, and await the result, in order to get the value you want.

console.log(await config());

But are you sure you want a dynamic import here?

Because this should do the same thing without any headaches at all.

import { config } from "../test";

edited Jan 21, 2022 at 4:59

answered Jan 21, 2022 at 4:51

Alex Wayne

188k52 gold badges328 silver badges363 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

Take Over a year ago

Thanks. Buit I got this error

Top-level 'await' expressions are only allowed when the 'module' option is set to 'esnext' or 'system', and the 'target' option is set to 'es2017' or higher.

I think I can't use await.

Alex Wayne Over a year ago

To use top level await you have to change your tsconfig as instructed by that error message. But you should be able to use await from inside any function without making those changes.

Take Over a year ago

I would like to use a dynamic import

Collectives™ on Stack Overflow

Why does async + await return AsyncFunction?

code

1 Answer 1

3 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

code

1 Answer 1

3 Comments

Your Answer

Sign up or log in

Post as a guest

Related