javascript: a bare call to a function whose import did not resolve is explained as 'receiver not typed' #1757

Symptom. When an import does not resolve, a plain call to the imported function is explained as "receiver not typed", although the call has no receiver. The real cause (the import '~/utils/price' was not resolved) is never named, so the answer points at the wrong thing to look at.

Repro. Any JS file whose import cannot be resolved (e.g. an alias with no config):

import { formatPrice } from '~/utils/price';
export default function handler() { return formatPrice(1); }

axiomcode path handler formatPrice →
`formatPrice` called in handler at server/api/price.js:2 — receiver not typed; if it is formatPrice, the chain is real

Expected: the reason names the unresolved import (specifier and file), e.g. "imported from '~/utils/price', which did not resolve".
Actual: "receiver not typed". Seen on three apps (a Remix app, a Nuxt-shaped app, a Vite app with a config alias).