ng generate component - catch clause variable is not an Error instance

[kaan35]

🐞 Bug report

Command (mark with an x)

• new
• build
• serve
• test
• e2e
• generate
• add
• update
• lint
• extract-i18n
• run
• config
• help
• version
• doc

Description

Hello

After adding server side rendering I can't create new component with cli command.

A clear and concise description of the problem... -->

🔬 Minimal Reproduction

npm i -g @angular/cli
ng new myapp && cd myapp
ng add @nguniversal/express-engine
ng generate component test

🔥 Exception or Error

An unhandled exception occurred: catch clause variable is not an Error instance
[error] AssertionError [ERR_ASSERTION]: catch clause variable is not an Error instance

🌍 Your Environment

Angular CLI: 14.1.0
Node: 18.6.0 (Unsupported)
Package Manager: npm 8.14.0 
OS: linux x64

Angular: 14.1.0
... animations, cli, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, platform-server
... router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1401.0
@angular-devkit/build-angular   14.1.0
@angular-devkit/core            14.1.0
@angular-devkit/schematics      14.1.0
@nguniversal/builders           14.0.3
@nguniversal/express-engine     14.0.3
@schematics/angular             14.1.0
rxjs                            7.5.6
typescript                      4.7.4

[damient]

I have the same error with angular 14.1

EDIT :
I tried with angular cli 14.0.7 and i have this error :
More than one module matches. Use the '--skip-import' option to skip importing the component into the closest module or use the module option to specify a module.
When i use 14.1 again with --module app it working fine

[ReponseDigitale]

Same behaviour when trying to generate a Pipe ng generate pipe foo.

And same workaround solution worked fine : ng generate pipe foo --module app

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}