Skip to content

build aot failed when having lazy load #2602

Closed

Description

@jjlgjkkl

there is a loadChildren in my project
export const routes: Routes = [
{ path: '', redirectTo: 'test01', pathMatch: 'full'},
{ path: 'test01', loadChildren: 'app/testing01/test01.module' },
when ng build --aot
exception occurred:

0% compiling can't resolve module D:/ng2/aotdemo/src/app/testing01/test01.module.ts from D:/ng2/aotdemo/src/app/testing01/test01.module.ts
can't find symbol MainModule exported from module D:/ng2/aotdemo/src/app/testing01/test01.module.ts
Error: can't find symbol MainModule exported from module D:/ng2/aotdemo/src/app/testing01/test01.module.ts
at ReflectorHost.findDeclaration (D:\Users\iminar\Dev\angular\modules@angular\compiler-cli\src\reflector_host.ts:200:15)
at _loop_1 (D:\Users\iminar\Dev\angular\modules@angular\compiler-cli\src\codegen.ts:62:45)
at CodeGenerator.readFileMetadata (D:\ng2\aotdemo\node_modules.npminstall@angular\compiler-cli\0.6.4@angular\compiler-cli\src\codegen.js:66:13)
at D:\Users\iminar\Dev\angular\modules@angular\compiler-cli\src\codegen.ts:105:56

i am using

"angular-cli": "1.0.0-beta.17",
@angular 2.0.2

Activity

  1. dev-johnny-gh commented on Oct 9, 2016

    @dev-johnny-gh

    +1

  2. hassanasad commented on Oct 10, 2016

    @hassanasad

    I could never get loadChildren to work so simply as loadChildren: 'app/testing01/test01.module' in webpack.

    I use something like this:

    loadChildren: () => new Promise(resolve => {
        (require as any).ensure([], () => {
            resolve(require('./testing01/test01.module').default);
        })
    })
    

    and then in the test01.module file

    export default class Test01Module { }
    

    But this might not work for --aot flag.

  3. filipesilva commented on Oct 10, 2016

    @filipesilva
    Contributor

    Dupe of #2452

  4. angular-automatic-lock-bot commented on Sep 6, 2019

    @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.

  5. locked and limited conversation to collaborators on Sep 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions