<p dir="auto">I've noticed some odd behavior in Deno.compile().</p>
<p dir="auto">The first time I compile a file it works more or less as expected.  But if I change or delete the source file and call Deno.compile() a second time I get the same result as the first time.  Apparently Deno is caching the source file.</p>
<p dir="auto">I'd like to do a fresh compile every time.  I'm purposely trying to push new changes out to web users.  I'd rather not call an external process to compile the TypeScript inputs before serving the JavaScript output to web users.  I guess I could, but I'd rather use the compiler API built into Deno.</p>
<p dir="auto">The caching is done within the process.  As soon as I restart my Deno process, the cache is clear.  The next time I call Deno.compile() it will reread the source file.  But only that next time.</p>
<p dir="auto">Deno is caching the input files, not the results.  So the compiler still takes a long time to run and it still produces a ton of warning messages.</p>
<p dir="auto">These are all local files.  Caching a local file will not save any resources.</p>
<p dir="auto">Ideal solution:  Deno.compile() would do no caching, or it would give me the option to explicitly clear the cache.</p>
<p dir="auto">At a bare minimum, add a note to the documentation so the next person doesn't get stuck.</p>
<p dir="auto">Thanks!</p>
<p dir="auto">Currently there is no way to internally cache bust with the compiler APIs, only if Deno is invoked with <code class="notranslate">--reload</code> will the compiler APIs cache bust.</p>