Where Does Psalm Store Config and Cache?
Psalm reads psalm.xml per project for error level and paths, caching analysis wherever configured with baselines for legacy code.
Last updated
Psalm configures per project through psalm.xml holding error level, scanned paths, and per issue handling. Analysis cache lives wherever configured, speeding repeat runs substantially.
Stale caches produce phantom findings after large refactors. Clearing cache trades one slow run for truth. Config files stay reviewable while caches remain disposable.
Where Psalm stores this, by platform
psalm.xml + cache dir
Error level plus paths config versioned per project. Cache speeds reruns. Clear on phantom findings.
psalm.xml + cache dir
Same repo relative config on Mac installs. Baselines commit beside XML. Ignore cache outputs.
Frequently asked questions
How do I clear the Psalm cache?
Delete the Psalm cache directory to force full reanalysis. The --no-cache flag runs clean once without deleting. Version bumps invalidate automatically.
How do I share Psalm config?
Commit psalm.xml with error level and paths while ignoring cache outputs. Baselines version beside it. Fresh checkouts configure from XML alone.
Notice an outdated path? Let us know.