Build creating nested dists

Description

This is a weird one, fellas.

A little background: I'm using ncc to build several GitHub Actions that are used for a deploy job. One of those actions needs to read in files from a /dist built through Webpack and then upload them to an AWS S3 bucket.

Behavior

The build output is creating nested dist files in each existing dist when there is a matching string "dist" in the script.

Here are examples of the two functions in my script which seem to be causing the issue:

const getFiles = () => {
  try {
    return fs.readdirSync(path.join(process.cwd(), 'dist'));
  } catch(e) {
    setFailed(`Failed to read dist: ${e}`);
  }
}

const readFile = (filePath) => {
  try {
    const absolutePath = path.join(process.cwd(), `dist/${filePath}`);
    info(`Reading file from ${absolutePath}`)
    return fs.readFileSync(absolutePath);
  } catch(e) {
    setFailed(`Failed to read file ${filePath}: ${e}`);
  }
}

Now, here's where things get weird. When I run ncc build (with the default /dist output) or ncc build -o dist, the build generates nested build directories inside of each build for each subsequent execution of the command, like:

|- dist
|-- dist
|--- index.js
|-- index.js
...

This will continue to generate nested build directories every time you run ncc build.

In the build output, it also converts the aforementioned functions getFiles and readFile in the following way, which may give some clue as to what is happening(?):

const getFiles = () => {
  try {
    return external_fs_.readdirSync(__nccwpck_require__.ab + "dist");
  } catch(e) {
    setFailed(`Failed to read dist: ${e}`);
  }
}

const readFile = (filePath) => {
  try {
    const absolutePath = __nccwpck_require__.ab + "dist/" + filePath;
    info(`Reading file from ${absolutePath}`)
    return external_fs_.readFileSync(absolutePath);
  } catch(e) {
    setFailed(`Failed to read file ${filePath}: ${e}`);
  }
}

This does not happen when I simply read from a directory with a different name. I have also tested with names other than dist and as long as the directory in the script matches the build output then this behavior manifests itself.

Workaround

To work around this, I have simply changed the output target to something like ncc build -o build and the issue goes away.

Run the shown ncc build commands with a source script that reads from a directory matching the output name, and compare them with the alternate build target. Trace the build entry point responsible for resolving that directory; done means repeated builds no longer create nested output directories while the generated bundle still reads the intended files.