Versions

@microsoft/bf-orchestrator-cli 4.14.1

Describe the bug

Orchestrator should not swallow underlying errors. For example in OrchestratorHelp.ts you see this code:

    } catch (error) {
      throw new Error(`Failed to parse ${filePath}`);
    }

This means you have no idea why parsing failed because error is not reflected.

To Reproduce

Steps to reproduce the behavior:

1. Create an LU file with improper syntax
2. bf orchestrator:create with that file

Expected behavior

You should see underlying parsing errors.

[bug]