clio run failure in windows 10 [Version 10.0.21387.1]

[Hugh]

Here is a screen capture:
`c:\Users\hsmyers\clio>clio new hello
Info: Added Clio dependencies
Info: Initialized new git repository.
Info: Initialization Complete!
Success: Run 'cd hello' to open, then 'clio run' to run the project!

c:\Users\hsmyers\clio>cd hello

c:\Users\hsmyers\clio\hello>clio run
Info: Creating build for node
× Error: Error: EINVAL: invalid argument, mkdir 'c:\c:'
Compilation Error: EINVAL: invalid argument, mkdir 'c:\c:'`

Expected behavior
I expected it to work.

Screenshots
If applicable, add screenshots to help explain your problem.

Versions (please complete the following information):

• Windows Version 10.0.21387.1
• Clio: 0.5.1
• Node: v14.17.0
• NPM: 6.14.13

Possible solutions
??!! Suggest you look at getting a windows box and actually using it.

[ibalbaert]

I have the same error for clio v 0.6.0
When the new project is on a different drive, for example d: , the error is:
× Error: Error: EINVAL: invalid argument, mkdir 'D:\D:'
Compilation Error: EINVAL: invalid argument, mkdir 'D:\D:'

[Hugh]

So would someone provide a link to the likely source of this obvious typo?

…

On Tue, May 25, 2021 at 9:58 AM ibalbaert ***@***.***> wrote: I have the same error for clio v 0.6.0 When the new project is on a different drive, for example d: , the error is: × Error: Error: EINVAL: invalid argument, mkdir 'D:\D:' Compilation Error: EINVAL: invalid argument, mkdir 'D:\D:' — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#207 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAHE7PUCUIEELUVPJNVP2XTTPPCK7ANCNFSM45ONQLTA> .

[ibalbaert]

I have installed and run successfully a new Clio v 0.6 project on Ubtuntu 20 and WSL2 in Windows.
But my main dev-box is Windows 10, so I can quickly test out any change/correction or new versions.

[Hugh]

Same here, although I run a bleeding-edge version of both windows and wsl (wsld in my case.)

…

On Wed, May 26, 2021 at 6:47 AM ibalbaert ***@***.***> wrote: I have installed and run successfully a new Clio v 0.6 project on Ubtuntu 20 and WSL2 in Windows. But my main dev-box is Windows 10, so I can quickly test out any change/correction or new versions. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#207 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAHE7PWKWSHA224JWXMAIHDTPTUWLANCNFSM45ONQLTA> .

[Pouya Eghbali]

I'll be working on a fix tonight, I will investigate the issue. Unfortunately I do not have a windows computer to test, but I guess I can just get a VM for a few hours.

[ibalbaert]

I have located the error: it occurs when executing the line 182
mkdir(destDir);
in the script build.js

In my case I'm working in folder D:\Clio\own_projects\hello - the value of variable destDir is the string D:\Clio\own_projects\hello\build\node ; the error is: × Error: Error: EINVAL: invalid argument, mkdir 'D:\D:'
Compilation Error: EINVAL: invalid argument, mkdir 'D:\D:'

[Hugh]

@ibalbaert Excellent work! Is your setup sufficient to do a build?

…

On Wed, May 26, 2021 at 11:18 AM ibalbaert ***@***.***> wrote: I have located the error: it occurs when executing the line 182 *mkdir(destDir);* in the script build.js — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#207 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAHE7PRCMI57IWKS7YO3GWLTPUUP5ANCNFSM45ONQLTA> .

[ibalbaert]

Should be possible to build, but as yet don't know how to fix the error.

[Hugh]

Let me take a look at build.js…

…

On Wed, May 26, 2021 at 11:36 AM ibalbaert ***@***.***> wrote: Should be possible to build, but as yet don't know how to fix the error. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#207 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAHE7PQU5REAVD5K4JG7PHLTPUWSPANCNFSM45ONQLTA> .

[Hugh]

Post a note when the change is available for a new install?

…

On Wed, May 26, 2021 at 12:15 PM Pouya Eghbali ***@***.***> wrote: Closed #207 <#207> via #208 <#208>. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#207 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAHE7PRR7JZQKPHJ5GJVDJTTPU3FDANCNFSM45ONQLTA> .

[ibalbaert]

I just tested with the new Clio from a few minutes ago: it works!

D:\Clio\own_projects\hello>clio run
Info: Creating build for node
√ Compiling source...
√ Adding Clio start script...
√ Installing npm dependencies (this may take a while)...
Hello World

[Hugh]

Same here! Great work Pouya!!

…

On Wed, May 26, 2021 at 12:23 PM ibalbaert ***@***.***> wrote: I just tested with the new Clio from a few minutes ago: it works! D:\Clio\own_projects\hello>clio run Info: Creating build for node √ Compiling source... √ Adding Clio start script... √ Installing npm dependencies (this may take a while)... Hello World — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#207 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAHE7PX5JD2G3SUDFSIG6GLTPU4B3ANCNFSM45ONQLTA> .