Can't use ng CLI to genereate a component in a library project

[eyalellenbogen]

Versions

Angular CLI: 6.0.0
Node: 8.11.1
OS: win32 x64
Angular: 6.0.0
... animations, cli, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router

Package                            Version
------------------------------------------------------------
@angular-devkit/architect          0.6.0
@angular-devkit/build-angular      0.6.0
@angular-devkit/build-ng-packagr   0.6.0
@angular-devkit/build-optimizer    0.6.0
@angular-devkit/core               0.6.0
@angular-devkit/schematics         0.6.0
@ngtools/json-schema               1.1.0
@ngtools/webpack                   6.0.0
@schematics/angular                0.6.0
@schematics/update                 0.6.0
ng-packagr                         3.0.0-rc.2
rxjs                               6.1.0
typescript                         2.7.2
webpack                            4.6.0

Repro steps

• Start a new app - ng new myApp
• From the new app's folder add a library project - ng g library someLib
• From the library folder - ng g c subComp

Observed behavior

Could not find an NgModule. Use the skip-import option to skip importing in NgModule.

Desired behavior

I would expect it to generate a component and register it in the main library module just like it does with a new application.

I couldn't find anything in the docs explaining if this is the right approach (I guess this is another issue). Is this by design?

[matheusdavidson]

Same here, its a bug:
#10653 #10672

[Brocco]

Closing...
Duplicate of #10653

[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.}