Static export of folders with index file creates html file with name of the folder

Bug report

Describe the bug

With Next 9 the new default is exporting paths as html files with the name of the path (see here).

However, this also has extended to folder with an explicit index file in them.

For example pages/folder1/index.jsx will get outputted as out/folder1.html this leads to webservers displaying the contents of that folder instead of the html file you would expect.

To Reproduce

1. Clone https://github.com/jaredpereira/next-export-bug-repro
2. npm i && npm run export
3. Inspect out or serve w/ now.sh

Expected behavior

The expected behavior is for pages/folder1/index.jsx , next export should output out/folder1/index.html

Additional context

Add any other context about the problem here.

[devisscher]

I think this is mentioned here. https://github.com/zeit/next.js#usage

You can add exportTrailingSlash option to your Next config and preserve the same functionality as before Next 9.

// next.config.js
module.exports = {
  exportTrailingSlash: true,
}

[jaredpereira]

@devisscher exportTrailingSlash results in every file being given it’s own folder with an index.html inside. That does resolve the problem in that it’ll work when served but it is a bit of an odd work around. The expected outcome here I think would be a 1:1 mapping of input files to output files, where index files are created when they exist in the input. I may be misunderstanding something obvious here though!