Angular 2: Wijmo component incurs Augury error in console

Angular 2: Wijmo component incurs Augury error in console

Posted by: ross-zhu on 14 September 2017, 11:56 am EST

• 

  ross-zhu

  • Post Options:
  • Link
    Copy

  Posted 14 September 2017, 11:56 am EST

  Dear support,

  I came across a problem while using Angular 2 + Wijmo with Chrome’s Augury plugin. To reproduce this issue:

  1. Create a page with any wijmo component. e.g. <wj-input-date>
  2. Open Chrome’s development console, and click Augury
  3. You will see error with following stacktrace:

  Uncaught TypeError: WjComponent is not an object!
      at module.exports (http://localhost:4200/polyfills.bundle.js:576:26)
      at Object.getMetadata (http://localhost:4200/polyfills.bundle.js:11972:43)
      at p (chrome-extension://elgalmkoelokbchhkhacckoklkejnhcd/build/backend.js:7417:26)
      at Function.Description.getProviderDescription (chrome-extension://elgalmkoelokbchhkhacckoklkejnhcd/build/backend.js:7441:17)
      at chrome-extension://elgalmkoelokbchhkhacckoklkejnhcd/build/backend.js:9255:47
      at Array.map (native)
      at getComponentProviders (chrome-extension://elgalmkoelokbchhkhacckoklkejnhcd/build/backend.js:9254:45)
      at Object.exports.transform (chrome-extension://elgalmkoelokbchhkhacckoklkejnhcd/build/backend.js:9172:22)
      at chrome-extension://elgalmkoelokbchhkhacckoklkejnhcd/build/backend.js:9205:48
      at Array.forEach (native)
      at transformChildren (chrome-extension://elgalmkoelokbchhkhacckoklkejnhcd/build/backend.js:9204:19)
      at Object.exports.transform (chrome-extension://elgalmkoelokbchhkhacckoklkejnhcd/build/backend.js:9220:14)
      at chrome-extension://elgalmkoelokbchhkhacckoklkejnhcd/build/backend.js:9205:48
      at Array.forEach (native)
      at transformChildren (chrome-extension://elgalmkoelokbchhkhacckoklkejnhcd/build/backend.js:9204:19)

  This error occurs no matter what Wijmo component you are using.

• 

  manish-gupta1

  • Post Options:
  • Link
    Copy

  Posted 14 September 2017, 11:56 am EST

  Hi Ross,
  
  Thanks for reporting the issue. We are able to the issue at our end. This issue has been escalated to the concerned team for further investigation with tracking id 245323 . We will let you know as soon as we get any update on this.

  Thanks,
  
  Manish Kumar Gupta

• 

  bertrandgaillard

  • Post Options:
  • Link
    Copy

  Posted 6 November 2018, 6:39 am EST

  Hi,

  I just tried again with all up to date (angular 7.0.1 / wijmo 5.20182.523 / augury 1.21.0) and it’s still failing like describe above…