Running the command yarn next-translate throws errors: "The syntax of the command is incorrect.", "Command failed: mkdir pages/cs"
New localised pages inside pages/[locale]/ dir.

Unfurtunately it seems like this library is incompatible with Windows by default.
I've hotfixed those issues by replacing "/" with "\" inside builder.js, but another errors have emerged (like undefined "rm" command...).
I use WSL bash now, it's working just fine in there.
Hey @matasek, yes, the CLI tool for static pages right now is only compatible in Unix. However, thank you to report it. A good consideration is to also support Windows for the CLI. Let's keep open the issue and I will take a look in a few days.
Hey @mataslib , this fix will be released on 0.14.0, however, you can try it now in 0.14.0-canary.1, please, can you confirm that it is working on your computer?
https://github.com/vinissimus/next-translate/releases/tag/0.14.0-canary.1
Thank you a lot 馃憦
Hello, I've tried it, it's not working properly yet. It now works in git bash (MinGW) 馃憤, however still does not work in Win cmd/powershell.
PS: I thank you!

Ok, in that case, I reopen the issue to fix this on 0.14.2 馃憤
I created a PR to fix the last issue. #111
I tested it on windows. It is working correctly.
@mataslib @heatseeker76 we created a prerelease 0.14.2-canary.2 with this fix! Can you verify that it works? 馃憦
@aralroca Great news! It works great now. Thanks! 馃憤
When I was testing it, I've just noticed that modifying files starting with underscore _(document|app).js does not trigger rebuild (in both cmd and bash so it seems to be non-related issue). Is this also happening to you?
@aralroca Great news! It works great now. Thanks! 馃憤
When I was testing it, I've just noticed that modifying files starting with underscore _(document|app).js does not trigger rebuild (in both cmd and bash so it seems to be non-related issue). Is this also happening to you?
Yes. It's a known problem commented on #56, the same thing is happening in /api routes.
Nevertheless, I think that we can fix it now. I'm going to change the milestone of #56 to 0.15.0 in order to prioritize the issue! Thanks to report it!
Hi @aralroca
Sorry I did not follow the PR I initiated. I was too busy at work and could not follow properly.
I installed and tested it and I just deployed the lastest version to prod.
@aralroca you are exceptional. The fact you took time to explain your change request says a lot about you. 馃挴
Thanks a lot !
Most helpful comment
Yes. It's a known problem commented on #56, the same thing is happening in
/apiroutes.Nevertheless, I think that we can fix it now. I'm going to change the milestone of #56 to 0.15.0 in order to prioritize the issue! Thanks to report it!