Hello, I am creating new project using ignightui-cli, follow steps, but at the end it fails to build.. can you check the script and tell me how to fix it.. It used to work.... I would think that cli supposed to create all that needed in the project directory.. it seems it does not.. 

C:\_ng\new_ig1\Sample>ig --version
_____ _ _ _ _ _____ _____ _ _____
|_ _| (_) | | | | |_ _| / ____| | |_ _|
| | __ _ _ __ _| |_ ___ | | | | | | | | | | | |
| | / _` | '_ \| | __/ _ \ | | | | | | | | | | | |
_| || (_| | | | | | || __/ | |__| |_| |_ | |____| |____ _| |_
|_____\__, |_| |_|_|\__\___| \____/|_____| \_____|______|_____|
__/ |
|___/

Ignite UI CLI version: 8.0.3
OS: Windows

C:\_ng\new_ig1\Sample>ig
Starting Step by step mode.
For available commands, stop this execution and use --help.

? Enter a name for your project: pj1
? Choose framework: Angular
? Choose the type of project: Ignite UI for Angular
Psst! Did you know you can also use our schematics package with Angular CLI to create and modify your projects?
Read more at: www.infragistics.com/.../cli-overview
? Choose project template: Default side navigation
? Choose the theme for the project: Custom
Generating project structure.
√ Project structure generated.
Git initialization failed. Install Git in order to automatically commit the project.

? Choose an action: Add component
? Choose a group: Grids & Lists
? Choose a component: Grid
? Choose one: Custom Grid
? Name your component: igGridUno
? Choose features for the igx-grid Sorting, Filtering, Row Editing
√ View 'igGridUno' added.

? Choose an action: Complete & Run
The project will be created using a Trial version of Ignite UI for Angular.
You can always run the upgrade-packages command once it's created.
? Would you like to upgrade to the licensed feed now? Yes
? Choose app host port: 4200
Build started.
Installing npm packages
Error installing npm packages.
Starting project.

> pj1@0.0.0 start
> ng serve -o "--port=4200"

An unhandled exception occurred: Cannot find module '@angular-devkit/build-angular/package.json'
Require stack:
- C:\Users\gkheysin\AppData\Roaming\npm\node_modules\@angular\cli\node_modules\@angular-devkit\architect\node\node-modules-architect-host.js
- C:\Users\gkheysin\AppData\Roaming\npm\node_modules\@angular\cli\node_modules\@angular-devkit\architect\node\index.js
- C:\Users\gkheysin\AppData\Roaming\npm\node_modules\@angular\cli\models\architect-command.js
- C:\Users\gkheysin\AppData\Roaming\npm\node_modules\@angular\cli\commands\serve-impl.js
- C:\Users\gkheysin\AppData\Roaming\npm\node_modules\@angular\cli\node_modules\@angular-devkit\schematics\tools\export-ref.js
- C:\Users\gkheysin\AppData\Roaming\npm\node_modules\@angular\cli\node_modules\@angular-devkit\schematics\tools\index.js
- C:\Users\gkheysin\AppData\Roaming\npm\node_modules\@angular\cli\utilities\json-schema.js
- C:\Users\gkheysin\AppData\Roaming\npm\node_modules\@angular\cli\models\command-runner.js
- C:\Users\gkheysin\AppData\Roaming\npm\node_modules\@angular\cli\lib\cli\index.js
- C:\Users\gkheysin\AppData\Roaming\npm\node_modules\@angular\cli\lib\init.js
- C:\Users\gkheysin\AppData\Roaming\npm\node_modules\@angular\cli\bin\ng
See "C:\Users\gkheysin\AppData\Local\Temp\2\ng-qeQMki\angular-errors.log" for further details.
(node:22508) UnhandledPromiseRejectionWarning: Error: Command failed: npm start -- --port=4200
at checkExecSyncError (child_process.js:643:11)
at Object.execSync (child_process.js:679:15)
at Function.execSync (C:\Users\gkheysin\AppData\Roaming\npm\node_modules\igniteui-cli\node_modules\@igniteui\cli-core\util\Util.js:273:36)
at Object.<anonymous> (C:\Users\gkheysin\AppData\Roaming\npm\node_modules\igniteui-cli\lib\commands\start.js:82:41)
at Generator.next (<anonymous>)
at fulfilled (C:\Users\gkheysin\AppData\Roaming\npm\node_modules\igniteui-cli\lib\commands\start.js:5:58)
at processTicksAndRejections (internal/process/task_queues.js:95:5)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:22508) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see nodejs.org/.../cli.html. (rejection id: 1)
(node:22508) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

C:\_ng\new_ig1\Sample>