no-await-in-loop eslint error on service-worker

[soullivaneuh]

I have a global eslint configuration for all my company projects.

It warns me at this part:

sapper-template/src/service-worker.js

Lines 25 to 27 in c0ca291

	for (const key of keys) {
	if (key !== ASSETS) await caches.delete(key);
	}

According to the rule: https://eslint.org/docs/rules/no-await-in-loop

Performing an operation on each element of an iterable is a common task. However, performing an await as part of each operation is an indication that the program is not taking full advantage of the parallelization benefits of async/await.
Usually, the code should be refactored to create all the promises at once, then get access to the results using Promise.all(). Otherwise, each successive operation will not start until the previous one has completed.

What do you think? Can this part be improve or is it a false positive?