sindresorhus/eslint-plugin-unicorn

`prefer-top-level-await`: Do not report cases where the promise is assigned to a variable

クローズ

#2,516 opened on 2024/12/24

 (3 件のコメント) (2 件のリアクション) (0 人の担当者)JavaScript (468 件のフォーク)user submission
enhancementhelp wanted

Repository metrics

Stars
 (5,022 個のスター)
PR merge metrics
 (平均マージ 4h 30m) (30d で 26 merged PRs)

説明

Description

Hello 👋, thank you for this great plugin :)

I have a case where I create a Promise on the top-level and assign it to a variable. Later, in an asynchronous function, I await the promise:

const preparationDone = prepareSomething();

export async function doSomethingThatNeedsPerparation() {
	await preparationDone;
	// ...
}

The motivation behind this is as follows: I don't want to use top-level await because I don't want to slow down the evaluation of the module scope. The result of the Promise must only be available at the time when the asynchronous function is executed.

Would it therefore be possible not to report cases in which the Promise is assigned to a variable?

Fail

run().catch(error => {
	console.error(error);
	process.exit(1);
});

Pass

const resultOfRun = run();

Additional Info

I know that the rule might be "too relaxed" in that case, but I still think that my use case is valid and should not reported as an anti-pattern :)

コントリビューターガイド