getStaticProps overrides exportPathMap

Bug report

Describe the bug

Adding getStaticProps overrides folder settings set within exportPathMap in next.config.js.

I’m essentially trying to get my html files to be output in /directory/index.html rather than /directory.html. Unfortunately even I set my exportPathMap to do so, as soon as the getStaticProps function is added in my script, the setting is overridden and the file will be output at directory.html

To Reproduce

git clone https://github.com/creativiii/next-js-export-bug
cd next-js-export-but
npm run build
npm run export

Then check the out directory.

Expected behavior

page-1 and page-2 should be respectively exported in /page-1/index.html and /page-2/index.html. Instead page-2 is exported as page-2.html.

System information

• OS: [e.g. macOS, Windows]: WSL Ubuntu 20.04
• Version of Next.js: [e.g. 6.0.2] 9.4.4
• Version of Node.js: [e.g. 10.10.0] LTS 12

[Timer]

Have you tried enabling this option?

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

[furcan]

getStaticProps is completely useless with next export. (Also exportPathMap)

I think the Next.js dev team is thinking the people around the world using the Next.js just to create a single “index.js” file, and print a “hello world!”

All the communication between the dev team and us is just like that: “We will not create a solution, use the Next.js just like that or else…”

Anyway, Thanks.