run ng generate lib for the first time

[BryanWilhite]

https://nrwl.io/nx/guide-nx-workspace =>

usage: ng generate lib <name> [options]
options:
  --directory 
    A directory where the app is placed
  --dry-run (-d)
    Run through without making any changes.
  --force (-f)
    Forces overwriting of files.
  --lazy 
    Add RouterModule.forChild when set to true, and a simple array of routes when set to false.
  --parent-module 
    Update the router configuration of the parent module using loadChildren or children, depending on what `lazy` is set to.
  --prefix (-p)
    The prefix to apply to generated selectors.
  --publishable 
    Generate a simple TS library when set to true.
  --routing 
    Add router configuration. See lazy for more information.
  --skip-package-json 
    Do not add dependencies to package.json.
  --skip-ts-config 
    Do not update tsconfig.json for development experience.
  --tags 
    Add tags to the library (used for linting)

[BryanWilhite]

it may be long-term important to mention that Nrwl Nx is originally intended to support Node exclusively on the server while my investments currently place Angular on top of ASP.NET Core

the Nx lib stuff would only come in handy for a multi-App workspace placing Angular on top of Node (and then Node could then call out to anything ...like ASP.NET Core)

[BryanWilhite]

consider moving that menu comp [GitHub] to a lib

also consider moving those static members in AnimationBuilderComponent [GitHub]

[BryanWilhite]

my relatively new songhay-ng-workspace repo uses the Angular-only library concept from the Angular 6.x time-frame

one of my issue comments in that repo indirectly links back to this issue

at this time i am not particularly interested in the nrwl-flavor of an Angular library and may leave this issue open just in case something comes up