[BUG] [Windows] Profile installation fails

[jnv]

Running superface install ... on Windows (PowerShell) fails with:

Error: ENOENT: no such file or directory, open ''
    Code: ENOENT

Expected Behavior

CLI should work.

Current Behavior

See the following output:

PS C:\Work\Superface\email-demo\superface> superface install address/geocoding --force
Installing profiles according to 'super.json' on path 'super.json'
⚠️  unable to parse super.json: Error: [
  {
    "code": "invalid_union",
    "unionErrors": [
      {
        "issues": [
          {
            "code": "unrecognized_keys",
            "keys": [
              "retryPolicy"
            ],
            "path": [
              "profiles",
              "communication/send-email",
              "defaults",
              "SendEmail"
            ],
            "message": "Unrecognized key(s) in object: 'retryPolicy'"
          }
        ]
      },
      {
        "issues": [
          {
            "code": "unrecognized_keys",
            "keys": [
              "version"
            ],
            "path": [
              "profiles",
              "communication/send-email"
            ],
            "message": "Unrecognized key(s) in object: 'version'"
          }
        ]
      }
    ],
    "path": [
      "profiles",
      "communication/send-email"
    ],
    "message": "Invalid input"
  }
]

Fetching profile address/geocoding from the Store
GET Profile Info address/geocoding
GET Profile Source File address/geocoding
GET compiled Profile address/geocoding
$ echo '<profile>' > 'C:\Work\Superface\email-demo\superface\grid\address\[email protected]'
$ echo '<compiled profile>' > 'C:\Work\Superface\email-demo\superface\grid\address\[email protected]'
    Error: ENOENT: no such file or directory, open ''
    Code: ENOENT
PS C:\Work\Superface\email-demo\superface>

Steps to Reproduce

1. Clone the email demo locally: https://github.com/superfaceai/email-demo
2. cd into email-demo/superface directory
3. Run superface install address/geocoding --force
4. Watch it crash and burn.

Your Environment

• CLI v0.0.22
• Windows 10
• PowerShell
• Node v12.16.3
• npm v7.12.0