-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Garbage collection for DENO_CACHE #1687
Comments
Yes, there's no automatic cache purge. I've been putting it off until someone asked for it : ) so thanks for asking. |
Side question: you run program with Deno, then you update Deno to newer version. Should program still run under new version without problems using old gen files? I believe I hit problem with this once, unfortunately can't reproduce it now. Of course purging cache helped the issue. |
Do you hava any idea for this issue? |
@bartlomieju The problem last time was due to native ES module upgrade. The source files were not changed so the hash keeps the same, although the compiled version is no longer runnable under new deno release. A way to fix this is to include deno version (or the last compatible version) along with the source file content for hashing. Regarding auto-purging-on-exit, we could possibly, instead of scanning the whole Alternatively, we can introduce an extra flag that cleans the out-of-date/invalid cache, like |
Adding a comment in the generated code that points to source location is a great idea! |
~/.gen
.~/.deno/gen
.
is that clear cash feature available on 1.0.0 ? |
~/.deno/gen
.
We have |
change a ts file and recompile it , the prev
xxxx.js
cached file in~/.deno/gen
is still there.I think it is some kind of
files leak
(deno
creates files but does not clean them when they are out of date).The text was updated successfully, but these errors were encountered: