Angular Cli 1.0.0-beta.11-webpack.8: ng build failed if route 'loadChildren'

[cuiliang]

https://github.com/angular/angular-cli/blob/master/addon/ng2/models/find-lazy-modules.ts#L38

.map((node: ts.PropertyAssignment) => {
        return JSON.parse(node.initializer.getText(source)); // tslint:disable-line
      });

JSON.parse failed with ：

loadChildren:'app/+workspace/+settings/settings.module#SettingsModule'

[mjolk]

"Unexpected token ' in JSON at position 0". :)

[LibertyBeta]

Can confirm and reproduce. Moving to ` removes the error, but causes routing to fail.

[monojack]

Do lazy modules work with a system.js build?

[cuiliang]

@monojack yes, works before update to angular-cli@webpack

[rosslavery]

Can confirm I'm getting the same thing using:

angular-cli: 1.0.0-beta.11-webpack.8
node: 6.5.0
os: win32 x64

[shaunlmason]

Same same.

angular-cli: 1.0.0-beta.11-webpack.8
node: 6.4.0
os: win32 x64

[coryrylan]

I believe the latest webpack branch ( beta.11-webpack.8 ) does not currently support lazy loaded modules yet.

[shaunlmason]

I believe the latest webpack branch ( beta.11-webpack.8 ) does not currently support lazy loaded modules yet.

You are correct in a way. RC5 apparently uses System.js to do the lazy loading, since the CLI moved to Webpack that method is unavailable. It looks like the RC2 router and RC6 resolve the issue. Unfortunately for me, the Angular 2 Material team is a bit out of sync, so I can't upgrade to RC6 yet.

I worked around it and implemented a basic async module loader for the time being.

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