sindresorhus/eslint-plugin-unicorn

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

已关闭

#2,516 创建于 2024年12月24日

 (3 条评论) (2 个反应) (0 位负责人)JavaScript (468 个派生)user submission
enhancementhelp wanted

仓库指标

星标
 (5,022 个星标)
PR 合并指标
 (平均合并 4小时 30分钟) (30 天内合并 26 个 PR)

描述

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 :)

贡献者指南