Don't create cache dir when `clean: true`

[lastmjs]

Could we possibly provide a way to disable the cache? I have my own caching built into the tool that I'm using this plugin to build, and I don't want the .rpt2_cache folder lying around afterwards, nor do I necessarily want the override of writing to the cache

[ezolenko]

What level are you caching at? Is it going to bypass typescript only or whole bundle? I'm caching both compiled code and diagnostic data, so most of the time unchanged files are not passed to typescript at all, while still repeating errors found on the previous run.

Otherwise a flag to disable caching should be easy enough to do.

[wessberg]

I would argue that the “clean” option should disable the cache. If the cache is cleaned for each rebuild, why cache at all? 😊

Another thing is that the cache depends on the npm package object-hash which doesn't support untranspiled async functions. I've added a pull request to fix this within the object-hash repo, but a simple fix would be to simply skip the cache step.

[ezolenko]

That's a good point, better than adding a new option I was originally planing to do :)

[ezolenko]

@lastmjs could you check if master works for you with clean: true?