All package imports resolve to a known package

An unresolved bare package import fails the production build the moment the bundler reaches the file, and if you ship via a platform that pre-builds only the routes it needs, the failure may surface mid-deploy rather than in local dev. AI models hallucinate confident-looking names from their training data — react-icons/fi when only react-icons/fa is installed, lodash when the codebase uses lodash-es, or outright typos like expres. Each one is a reference-integrity failure the tsconfig and bundler cannot silently paper over.

Confirm each flagged import names a package that exists on npm before trusting it, then either install it or correct the specifier. Run the verification and install in one pass:

npm view react-icons
npm install react-icons

For workspace packages, declare the package in the root package.json workspaces field so resolution finds the sibling directory.