console.log(__dirname + '\dist\');
deleteEmpty(__dirname + '\dist\')
.then(deleted => console.log(deleted)) //=> ['foo/aa/', 'foo/a/cc/', 'foo/b/', 'foo/c/']
.catch(console.error);
gulp remove failde

The "package.json" file reports the Node engine requirement as node@>=6. However, your use of async/await functionality actually requires node@>=7.6.0.

Please either eliminate the use of the async functions or else correct the Node engine requirement in your "package.json". My personal preference would be to remove the async functions... although they are awesome, it is more frustrating to not be able to use a good utility library because of it requires such a modern version of Node only due to syntactic sugar.

Thanks!

Running deleteEmpty.sync('/mydir') is resulting in the following error output for me:

Error: Cannot find module 'matched'
    at Function.Module._resolveFilename (module.js:337:15)
    at Function.Module._load (module.js:287:25)
    at Module.require (module.js:366:17)
    at require (module.js:385:17)
    at Function.getter [as glob] (/Users/robertgryzynger/Sites/Meyers8/deploy/docroot/themes/custom/meyers/node_modules/lazy-cache/index.js:34:42)
    at Function.deleteEmpty.sync (/Users/robertgryzynger/Sites/Meyers8/deploy/docroot/themes/custom/meyers/node_modules/delete-empty/index.js:58:19)
    at /Users/robertgryzynger/Sites/Meyers8/deploy/docroot/themes/custom/meyers/gulpfile.js:119:18
    at taskWrapper (/Users/robertgryzynger/Sites/Meyers8/deploy/docroot/themes/custom/meyers/node_modules/undertaker/lib/set-task.js:13:15)
    at bound (domain.js:280:14)
    at runBound (domain.js:293:12)

I'm using what appears to be the latest version: 0.1.3.

When I require the module and use it in my code, it logs via log-ok but I do not want these logs in my app output.

How can we do that?

If cb() throws an error, it will be called again within the error object.

Why does it use so many resources for a simple task?

Calling the asynchronous deleteEmpty() produces different results than calling the synchronous deleteEmpty.sync() on the same directory.

Example:

src/file.txt
src/foo/
src/foo/bar/

Synchronous

deleteEmpty.sync('src/') produces the following result:

src/file.txt

In the synchronous case src/foo/bar/ is deleted first. Since src/foo/ is now empty, src/foo/ is deleted as well. This is the behavior I expected.

Asynchronous

However deleteEmpty('src/', cb) produces the following result:

src/file.txt
src/foo/

So in the asynchronous case the empty directory src/foo/ is left behind. I would expect src/foo/ to be deleted as well.

deleteEmpty('foo/')
  .then(deleted => console.log(deleted)) //=> ['foo/aa/', 'foo/a/cc/', 'foo/b/', 'foo/c/']
  .catch(console.error);

does nothing to the folder if we are in version 3.0.0, outputs undefined

This error should be passed to the callback.

This doesn't work

deleteEmpty('folder/');

But this does:

deleteEmpty('folder/',function(){});

After some experimenting with your plug-in, I found out why I couldn't get it to work: Mac OS automatically adds a hidden .DS_Store file in each folder. When I manually deleted that file from my (otherwise) empty folders, the recursive deletion worked fine. I think it's safe to delete folders even if it contains a hidden .DS_Store file.

(.DS_Store is a file that stores custom attributes of its containing folder, such as the position of icons or the choice of a background image.)

I upgraded from 2.0.0 and has stopped working!

Looking for solutions, I find another issue about the same problem where the author (@jonschlinkert) said that "[...] this was refactored" and closed it.

What does it means? Where are the patch release?