fs.readdir returns file 'dist' with 3.0.0-beta.11

Is this a BUG or a FEATURE REQUEST?: BUG

What happened: When running fs.readdir for a certain directory path, let’s say /example/dir, if I run the nexe application from under that same directory path, let’s say /example/dir/testNexe, fs.readdir will return a dist file that does not exist. This is the path returned by fs.readdir:

/example/dir/testNexe/dist

What you expected to happen: fs.readdir should not return a file that does not exist when running the nexe app from a directory under the one passed to fs.readdir

How to reproduce it (as minimally and precisely as possible):

• Call fs.readdir with a path (i.e. /example/dir) in a packaged nexe application
• Log result returned from fs.readdir
• Run the nexe application from a directory under /example/dir (i.e. /example/dir/testNexe)
• /example/dir/testNexe/dist is logged and should not.

Anything else we need to know?:

• This doesn’t happen when running the nexe application from a directory not under the directory passed to fs.readdir
• This doesn’t happen with nexe 2.0.0-rc.34
• This is happening on both OSX Mojave and Debian 7.

Environment

• Platform(OS/Version): OSX Mojave, Debian 7
• Host Node Version: 8
• Target Node Version: 8
• Nexe version: 3.0.0-beta.11
• Python Version: 2.7.10

[ArashMotamedi]

fs.promises.readdir works!

[anmonteiro]

I tried with 3.0.5 and it produced the same results btw.