When using mkdocs serve locally with uncommitted files, the mkdocs live/hot reload feature will monitor the changes in the .cache directory, causing a live reload infinite loop.
This can be confirmed by monitoring the changes. I'm not sure why the mkdocs file monitoring continues during build.
When using
mkdocs serve
locally with uncommitted files, the mkdocs live/hot reload feature will monitor the changes in the.cache
directory, causing a live reload infinite loop.This can be confirmed by monitoring the changes. I'm not sure why the mkdocs file monitoring continues during build.
I will open a PR to fix this.
Potentially related: https://github.com/mkdocs/mkdocs/issues/2519