The message for the different version is just that – something to be aware of, but doesn't necessarily mean anything is wrong. The update process linked by @Teodosia will bump to the latest and should also update the Ignite UI for Angular package too. So the message will likely be gone for now at least.

Explanation:
As there are commands that make modifications such as adding new components, the Ignite UI CLI is included locally in the project (as a dev dependency). Commands inside the project are handed off to this local version. Doing this allows for projects that haven't been updated yet to whatever version you've installed globally (e.g. project is still using Angular 11 while your global version would use 12 or the other way around) and ensures the results produced are compatible with the project state.

That's why you see the message and different version when you run outside the folder – in the latter case there's no project with local installation and thus the global one executes the command. The same principle is used in the Angular CLI and the same behavior can be observed when running `ng` commands btw 🙂

Hello Michael,

Late reply (misconfigured notifications on my end), but as with my previous post the Ignite UI CLI was updated the following week as expected, with updated templates for 12.1 (https://github.com/IgniteUI/igniteui-cli/releases) so you can grab new versions.

PS: Through GitHub you could even subscribe to get notified of release if that interests you – there's a Custom condition for Releases under the Watch feature 🙂

Hello Michael,

No need to try other things, as the problem I believe has presented itself at this point. New projects templates don't include node_modules (and there's quite a bit of those Angular projects rely on these days) as every creation goes through an install step. If that fails, of course some/all modules will be missing and the project won't run.
I guess we can probably handle this case better in the CLI, but it did give the indication of the problem:

[quote user=”0807E5E031A3E3AD16C7C764F256184CB42D983D”]? Choose app host port: 4200
Build started.
Installing npm packages
Error installing npm packages.[/quote]

And after you tried to manually run npm install the error is detailed enough – the same one as in the previous thread linked in a reply above and the solution for the short-term is the same: update "jasmine-core" to "~3.8.0" (and while at it you might want to adjust “karma-jasmine-html-reporter” to use tilde range like "~1.7.0" to avoid future trouble. After this npm i should be able to correctly install and the project should run.

In case you are wondering – the templates used for new Angular projects are shared between the Ignite UI CLI and our Angular schematics, so getting the same result is not surprising. The project templates in the current version are based on Angular CLI 12.0.x templates, which as discussed in the previous thread shipped with relaxed version range for the "karma-jasmine-html-reporter" package. So when a new version of that came out it got picked up and caused this trouble when installing with Node.js 16 since it does additional peer dependency checks.
That issue has been resolved in the Angular CLI and we're updating to the latest version on our end. New versions of both CLI and schematics updated to 12.1 should be out soon (most likely start of next week).