Unresolved imports
What an unresolved-import finding of fallow dead-code means, why it matters and how to fix it.
What it reports
Import could not be resolved.
Dead code explains how fallow finds it.
Why it matters
When the runtime or the bundler cannot resolve the path either, the build fails or the module throws when it loads. fallow also loses the edge, so the files behind it can show up as unused.
Example
src/app.ts imports ./routes/admin, but no matching file exists after extension and index resolution.
Fix
Fix the specifier, restore the missing file, install the package, or align tsconfig path aliases with the runtime resolver.
Facts
| Fact | Value |
|---|---|
| Issue type | unresolved-import |
| Rule id in SARIF output | fallow/unresolved-import |
| Command | fallow dead-code |
| Default severity | error |
Config key in rules | unresolved-imports |
| Filter option | --unresolved-imports |
| Suppression comment | // fallow-ignore-next-line unresolved-import |
Fixable with fallow fix | No |
| Opt-in | No |