You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not really. The cache key already contains the full target path. However if the user deletes a target file, that is not taken into the account - and Shake thinks that file need not be recreated because it is cached (at least, that's my theory).
Probably to do with symlinks. To test this theory, resolve the filepath to remove any symlinks before using it in cacheKey and cacheClosure (Rib.Shake.writeFileCached).
EDIT: Just check for missing files, and invalidate their cache. To reproduce, rm -rf ./b and re-run the app.
Different target directories use the same Shake cache.
The text was updated successfully, but these errors were encountered: