Accounting for asynchronous operations about unused-filename

[sindresorhus]

Even if it did that, there's no guarantee that the file system is not already out of sync from your expectations and the filename has been used.

[fabiospampinato]

If I'm understanding this correctly you're kind of saying that since there would still be issues to take into consideration, which would be outside of the scope of this library, it would probably be better to handle this particular issue and all the others together outside of this library? 🤔

If so I'd be happy to close this issue and handle it and the other issues in a separate write-to-unused-filename package.

[sindresorhus]

Exactly. Happy to link to your module if you make it.

[fabiospampinato]

👍 I'll post a link to it here when it's published.

[fabiospampinato]

5 months later (🙀), but here it is: write-unused-path. In the end I thought it made sense to write get-unused-path too. While I was at it I got a little carried away and I rewrote filenamify too, but instead of stripping out forbidden characters it replaces them with similar-looking unicode characters, I'm not sure if that's actually a good idea but I'll give it a try.

I'm closing the other issue I opened in this repo as I don't need it anymore.