You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was not able to plug-in a new Component/Animation at run-time without building my own distribution because the Kute Execution Context (KEC) is not exported in the KUTE namespace. According to your own code and the example. onStart functions should register the property-updating function in the KEC, but for this to happen, the KEC needs to be available.
I worked around this by modifying your exported KUTE object to include KEC,
I haven't had the time to check on KUTE.js in the last couple of months, last time I was, it was a beginning of a Typescript rework, which had an unfortunate ending caused by loss of data. The KEC is attached to the Window object by one of the core functions, but I wonder, are you trying to integrate with some SSR framework?
I'm thinking of a full rework to easily integrate any framework and/or headless systems. I'm open to any suggestion!!
Thanks ❤️
I was not able to plug-in a new Component/Animation at run-time without building my own distribution because the Kute Execution Context (KEC) is not exported in the KUTE namespace. According to your own code and the example.
onStart
functions should register the property-updating function in the KEC, but for this to happen, the KEC needs to be available.I worked around this by modifying your exported
KUTE
object to includeKEC
,and then qualified my references to
KEC
withKUTE
in the definition of myonStart
function for my component:The text was updated successfully, but these errors were encountered: