Multiple entryModule support

From @artonge on May 7, 2018 14:51

Bug Report or Feature Request (mark with an x)

- [ ] bug report -> please search issues before submitting
- [x] feature request

Area

- [x] devkit
- [ ] schematics

Versions

node version: v9.4.0 npm version: 5.6.0 Linux (Ubuntu 17.10)

Repro steps

Clone this example: https://github.com/artonge/multiple-entrymodules

The log given by the failure

At execution in the browser I have: Uncaught Error: No NgModule metadata found for 'AppModule'. This error only appears for the module that wasn’t specified has the entryModule in the webpack config.

Desired functionality

At my company our webpack config has two entry points for two different apps, and generate two bundles for the two apps. The problem is that when using AOT, we can only specify one entryModule, but the two apps have different entryModule. It would be nice to specify two entryModules so the metadata are generated for both of them.

Copied from original issue: angular/devkit#861

[Rush]

I would love to find a solution as well.

[jetfontanilla]

if you need an option for multiple paths instead of multiple entry modules, I’ve forked @rush (based from @artonge) and added this feature https://github.com/jetlogs/angular-cli

npm install @jetlogs/webpack

import { AngularCompilerPlugin } from "@jetlogs/webpack";


new AngularCompilerPlugin({
    tsConfigPath: "tsconfig.json",
    paths: [
      "/path/to/entry1.ts",
      "/path/to/entry2.ts"
    ]
})