Is deno's cache philosophy coherent for local files ?
I'm new to deno and surprised that it will cache local files that are imported and not update the cache when those files change. This is particularly painful when tying to use deno in Jupyter. I assume that a good cache should be transparent to the user (developer in this case). If I want the cache to be further optimized so it no longer behaves like a normal cache but require manually tracking dependencies then I should have to enable an option or do something explicit. But maybe I am not understanding the design philosophy of deno ? It would be nice if there were an easy way to stop deno caching local files during development of jupyter notebooks. It would be even better if deno could check the date of the files and maintain a coherent cache for local files.
