Problem
The dependency checker flags bold words in stack/tech sections as missing dependencies. Words like "Vercel", "S3", "OAuth", "REST API", "WebSocket", "Tailwind CSS" etc. get DEPENDENCY_MISSING warnings because they're not in package.json and not in the KNOWN_RUNTIMES set.
Where to look
src/drift/checkers/dependency.ts — the KNOWN_RUNTIMES set at the top of the file.
What to do
Expand the set to cover common non-package terms that appear in stack documentation: cloud providers, protocols, architectural terms, CSS frameworks mentioned by name but installed under different package names, etc.
Alternatively, consider whether a config-based ignore list would be more maintainable long-term.
Acceptance criteria
- Common non-package terms no longer produce false
DEPENDENCY_MISSING warnings
- Existing tests still pass
- Add test cases for the new entries
Problem
The dependency checker flags bold words in stack/tech sections as missing dependencies. Words like "Vercel", "S3", "OAuth", "REST API", "WebSocket", "Tailwind CSS" etc. get
DEPENDENCY_MISSINGwarnings because they're not inpackage.jsonand not in theKNOWN_RUNTIMESset.Where to look
src/drift/checkers/dependency.ts— theKNOWN_RUNTIMESset at the top of the file.What to do
Expand the set to cover common non-package terms that appear in stack documentation: cloud providers, protocols, architectural terms, CSS frameworks mentioned by name but installed under different package names, etc.
Alternatively, consider whether a config-based ignore list would be more maintainable long-term.
Acceptance criteria
DEPENDENCY_MISSINGwarnings