Summary

The recent fix to stop flagging import aliases (import { fun as bar } from "./my-module") resolved the false positive for single-specifier imports. However, the rule still incorrectly flags as when it appears in a multi-specifier import, even though it is unambiguously an import alias and not a type assertion.

Example

The following import triggers a false positive:

import { A as B, C } from '@lib';