Fix file URL error on Windows

[ericx20]

On Windows, create-cubing-app errors out. Here is an example:

PS C:\Users\ericx> npm create --yes cubing-app@latest my-cubing-project
---------------------------------
Creating a cubing project in the following folder:
my-cubing-project

node:internal/process/esm_loader:40
      internalBinding('errors').triggerUncaughtException(
                                ^

[Error: ENOENT: no such file or directory, lstat 'C:\C:\Users\ericx\AppData\Local\npm-cache\_npx\8f9f419572216059\node_modules\create-cubing-app\app-template'] {
  errno: -4058,
  code: 'ENOENT',
  syscall: 'lstat',
  path: 'C:\\C:\\Users\\ericx\\AppData\\Local\\npm-cache\\_npx\\8f9f419572216059\\node_modules\\create-cubing-app\\app-template'
}

Line 69 of bin/create-cubing-app.js throws an error because of the leading slash on appTemplatePath.
For some reason on Windows, that makes Node fs.cp access a bad path with a double C:\. On Linux the leading slash works fine.

Solution is to use Node url.fileURLToPath to ensure the URL is a proper absolute path on different platforms. On Windows it removes the leading slash like so:

• before: '/C:/Users/ericx/Documents/dev/create-cubing-app/app-template'
• after: 'C:\\Users\\ericx\\Documents\\dev\\create-cubing-app\\app-template'

[lgarron]

I'm happy to support Windows, but I don't have an easy way to test for it. Could I ask you to also add a GitHub action on Windows testing that project creation works, as well as a build in the created folder? That would catch any regressions.

[ericx20]

Good idea! I've added an action for that. Let me know if you need any further changes.

[lgarron]

Thanks! 😊