Open Maritims opened 7 years ago
also having this issue
this issue is happening to me when I switch back and forth between two modules.
same here
[HMR] App is up to date. vendor.js?v=lUHzoJv-0LCJm8IVcLeBLU01Ca9mipNkf7qqbacVnoM:117780 Unhandled Promise rejection: Cannot read property 'nativeNode' of null ; Zone: <root> ; Task: Promise.then ; Value: TypeError: Cannot read property 'nativeNode' of null
Had same error.
In hybrid application, downgraded (footer) component was registered twice in a module. So Angular throw this error, when tried to delete this component for second time
@Maritims were you able to resolve this issue?
@Maritims were you able to resolve this issue?
Sadly no. I've stopped working with Angular since for many reasons.
Have the same error with hybrid app. Angular throws this error when app goes from the page that has downgraded component.
@antontemchenko were you able to fix that?
Have the same error with hybrid app. Angular throws this error when app goes from the page that has downgraded component.
@antontemchenko were you able to fix that?
@Andrii-A As i wrote earlier, in my case this error showed up when downgraded component was registered twice. So looking for duplicated registration of the component in module and removing duplication resolved the problem.
Thank you! I found that I had the same problem - I registered the same component as downgraded directives with different names.
Fixed problem. In my case the problem was including in template a micro-tag as custom elements into another.
We're getting up and running with angular-hmr in our existing ng2 project but are experiencing a rather puzzling issue. Google has nothing to tell us on this matter. The error is as follows and I hope you can aid us in understanding why this is happening.
This behaviour occurs when we alter any code file in order to trigger a hot update.