title: Benefits of Angular libraries vs Angular modules in a monorepo? NX architecture
body: <p>I'm wondering what are the benefits of working with libraries rather than modules in Angular, as nx.dev recommends for an monorepo architecture.</p>
  <p>I understand the benefits for a npm publishable feature like interfaces that another repo will consume, but why would I want to make a library out of a business related feature, like a homepage, for example :</p>
  <pre><code>myorg/
  ├── apps/
  │   ├── todos/
  │   └── todos-e2e/
  ├── libs/
        ├── todos/
          ├── home/   &lt;-- why nx recommends making a library here?
            ├── src/
              ├── lib/
                ├── home.component.html/ts/scss
                ├── home.module.ts
  ├── tools/
  ├── README.md
  ├── workspace.json
  ├── nx.json
  ├── package.json
  </code></pre>
  <p>rather than</p>
  <pre><code>myorg/
  ├── apps/
  │   ├── todos/
           [...]
           ├── home/   &lt;-- just a simple lazy loaded module here
             ├── home.component.html/ts/scss
             ├── home.module.ts
  │   └── todos-e2e/
  ├── libs/
  ├── tools/
  ├── README.md
  ├── workspace.json
  ├── nx.json
  ├── package.json
  └── tsconfig.json
  </code></pre>