`tmp` should use `{ recursive: true }` when available with `unsafeCleanup: true` about node-tmp HOT 5 CLOSED

Thanks for the report @hasezoey.

In the past, I first tested the { recursive: true } option, however, I turned out that it would sometimes fail or did not behave in the way we needed it to, with the then available node version.
That is why we, reluctantly, incorporated rimraf.

I will see what this option does now and whether it behaves the way we need it to.

from node-tmp.

As for the removeCallback not being in sync is a question of the OS you are working under. Windows will lock open files and thus prevent rmdir from removing the directories these files are located in.
Sometimes, this goes as far as that node has to be shutdown prior to the lock being removed, leaving all directories in place, and one has to manually clean up the temporary storage.

from node-tmp.

Windows will lock open files and thus prevent rmdir from removing the directories these files are located in.

just for information, i am on Linux, so they should be unlinked if not directly removed (which recursively deleting (at least rm -rf) does)

from node-tmp.

Thanks for the information. I will see what I can do.

from node-tmp.

rimraf works for me and also in the automated tests

please provide a more specific scenario in which this will not work.

from node-tmp.