when run "npm run build", index.html file only exists in build/xxx/en/ dir, but not copied to the root dir

[loveky]

Is this a bug report?

Not Sure

Have you read the Contributing Guidelines?

Yes

Environment

Windows 7
Node 6.9.5
npm 3.10.10

Steps to Reproduce

(Write your steps here:)

1. Follow the installation process
2. run npm run build
3. check the build directory

Expected Behavior

Want to see my index.html file in build/my-site-name/ directory. This behavior is documented at HERE

Actual Behavior

the index.html only appears in build/my-site-name/en directory

Reproducible Demo

Pleace check Steps to Reproduce

[JoelMarcey]

Hi @loveky! Interesting. I followed your process and I see an index.html file in the root build/site directory. Do you have a repo I can look at to try to reproduce exactly?

[Happy-Ferret]

Same issue here.

Repo: https://github.com/Anima-OS/dev-corner

[Happy-Ferret]

I just tried doing the same on another machine, using just the default example and can reproduce this behavior.

[Happy-Ferret]

I just checked again, this time using WSL (Windows Subsystem for Linux), because I had already suspected it might be due to a Windows specific bug.

Sure enough, there it generates the correct output.

[Happy-Ferret]

Curious. I spend some time debugging the issue via VS Code earlier this morning.

Changing

writeFileAndCreateFolder(targetFile.replace('/en/', '/'), str);

on line 466 in generate.js

to

writeFileAndCreateFolder(targetFile.replace('en', '/'), str);

Seems to fix the issue.

Albeit that's clearly a hack and the proper way to fix this would probably just involve implementing the fix on line 437.

Namely, TODO: use path functions

[JoelMarcey]

@Happy-Ferret Hi. Would you mind integrating #490 into your local repo and see if it fixes this problem for you?

[Happy-Ferret]

I'll gladly test it once I'm back at the office, two hours from now.