-
Notifications
You must be signed in to change notification settings - Fork 12k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AOT lazy loading: Error: Cannot find module #7153
Comments
related to: #2452 maybe ? |
I tried two Webpack configurations: one with AOT and one without. Still getting the same error. So I don't know if this is really an AOT issue. |
I report this also, android build. |
I fixed it in my codebase, but it is probably a different error: had a link to the same |
also missed a warning in the build, which I fixed using the following plugin:
not sure if this helps in your case or not. |
@MovGP0 is that resolving this warning? I'm asking, because I have this same issue with paths not resolving in my lazy modules, so I'm wondering if that is the issue.
If so, I'm getting it. Is there something I need to do to remove that warning in my app? If so, where do I put that? |
Is this still reproducible? |
Closing the issue due to inactivity. If the problem still exists in the latest version of the CLI, please open a new issue following the template and providing a minimal demo where we can reproduce it. Thanks! :-) |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Bug Report or Feature Request (mark with an
x
)Versions.
Output from:
ng --version
.angular-cli: 1.0.0-beta.10
node: 6.10.0
os: win32 x64
Repro steps.
build using ngc, then compile angular using aot. Run app. try to visit lazy loaded module path.
The log given by the failure.
Here is my app.routes.ts
Tsconfig.aot.json
webpack config
Regular routes work fine, but lazy route cannot find the module. Path is correct relative to app.routes.ts
The text was updated successfully, but these errors were encountered: