Caridy Patiño
Caridy Patiño
@pmdartus what is missing here? when do we plan to merge this?
@pmdartus with this refactor, is there a need for `vnode.vm` anymore? I think it is important for us to remove that pointer, which is set lazily and used only in...
@jodarove ping
cc @leobalter this is the issue related to our conversation yesterday. @pmdartus do you have more context here?
I'm still very much confused about what this does, and why it does it?
By looking at the error message, this seems like a problem with proxies. Promise.prototype.then expects a branded promise object, but it is receiving a proxy of it most likely, which...
cc @seksenov @manuel-jasso to see if he can re-route this issue to the proper queue, this is definitely not LWC.
@AllanOricil it means that we will not fix it in current production code, but in the upcoming release only, which might take a while to hit production.
@larkintuckerllc when registering LWC as WC you must build it accordingly, change this line: `window.customElements.define('my-app', App);` into `customElements.define('my-app', buildCustomElementConstructor(App));` Make sure that you import `buildCustomElementConstructor` from lwc. As for the...
Yes, this is the right repo for this kind of issue, because the problem here is an intersection between components and engine. In this case, you're facing an issue related...