The check you are mentioning is worthwhile, I thought that a call to cachify.cachify_js and cachify.cachify would exercise that code path since they have to access the files to generate the SHAs which are placed in the URLs.

From my understanding, the connect-cachify middleware itself shouldn't actually access the file but convert a cachified URL to a non-cachified URL so another middleware can handle the request.