Knockout: Unable to process binding afterRender due to Vue Collision(?)

[f1729]

Hello!
We currently manage a Vue(2.x) application, which is injected into other web applications, so we do not have much control of the libraries they use. In this case (Magento 2.x) they use knockout.js and we have this problem, which I do not have much idea about and I would like them to help me understand what could be happening.
Thank you.
Update: (this error is shown first)

[hdegues]

Hi
I have the same problem

[mbest]

This is an error within your main.js code. Knockout is simply reporting that there was exception from that code while applying bindings.

[f1729]

@mbest This application injected into other pages has no problems, so it seems strange to me that this one with knockout.js has this error

[chrisknoll]

That may be, but the exception is buried inside main.js (from your stack trace) or somewhere below init in after-render.js. Set a breakpoint in the main.js and try to understand why p.a is not a constructor. You have the breakpoint there, what is p.a?

[f1729]

@chrisknoll Thanks for read.
p.a is ...

[PaulHuizer]

see here example
Shouldn't the code be:
FingerPrint2().get ...

[mbest]

Please feel free to continue the discussion, but I'll close this since it's not an issue from Knockout.

[f1729]

@PaulHuizer to load it as a module we have to use the new
In addition to having problems with Webpack 😕
It seems to be related to this
https://github.com/Valve/fingerprintjs2/issues/233

[PaulHuizer]

Ok, good luck with it ;-) I just saw this remark and thought .. it might have been missed:

Fingerprint2.get is now a static function. It replaces new Fingerprint2().get.

[GrosSacASac]

What is the ouput of npm ls --depth=0 ?

[f1729]

@GrosSacASac OMG Thanks, I just realized that I was using [email protected], I just updated to the version [email protected].
I can not confirm that the error is corrected because our partner deactivates our application, I will be alerting when I have news. Thank you very much to all!