-
Notifications
You must be signed in to change notification settings - Fork 75
Bug with angular-cli #57
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
Comments
It's only with lazy loading routes |
Hi, it seams that it could be more general issue: angular/angular-cli#4246, nevertheless I will have a look on that. |
Re, |
Ok here are some test i did such as i didn't install angular2gridster with npm but integrate the source with my project like your demo page and things work fine. Thinks it's something weird about the webpack version you included in your package as dependencies. |
Can you send me which version of angular cli you use? |
I've used 1.0.4 before and now used 1.2.0 |
I had the same problem and I'm sure it has something to do with webpack versions. I managed to solve the problem by installing the angular cli locally before running normal npm install. I noticed that if I installed normally, angular cli would have webpack in its node_modules folder but not if I installed the it first. |
I have similar problem. We also have many LazyLoading modules in our project. Angular - 4.2.5
|
same issue here
package.json:
ng serve
|
It could be afected by |
Try to fix bug with angular-cli #57
You were right. It seamed to be webpack dependency issue. It should be fixed in v.0.6.4. |
It seems like everything work just fine. |
Hi,
Here is the step to reproduce the bug :
Output :
Error: No module factory available for dependency type: ContextElementDependency
at Compilation.addModuleDependencies.
Cheers,
The text was updated successfully, but these errors were encountered: