This would be good, but at a minimum the command queue system should be fixed to, for example, lazily load the sdk and reliably queue up the command to open the widget when clicking a custom element.
[Featurebase SDK] Messenger not initialized. Please call 'boot' first.
The above warning is logged when calling ‘open’ after calling ‘boot’. I have to implement a hack where I use setInterval to watch for the featurebase iframe to load.
Javier
•
Jul 11, 2024
Hey folks, any news regarding this matter? I’ve noticed that the app used to download 1.1 MB whereas it is on the 1.6 MB mark these days.
It’s not getting better and it is impacting our user experience.
Do you have short-term plans to alleviate the load, or make the whole widget SSR?
Atiq Gauri
•
Mar 21, 2024
Does this needs to be enabled in widget intialization or it enabled by default?
Bruno H
Team•
Mar 21, 2024
This feature is not yet available, but we're planning to add an option to toggle it on once it is released.
Log in to comment and vote
Comments4
taylor
Jan 17
This would be good, but at a minimum the command queue system should be fixed to, for example, lazily load the sdk and reliably queue up the command to open the widget when clicking a custom element.
The above warning is logged when calling ‘open’ after calling ‘boot’. I have to implement a hack where I use
setIntervalto watch for the featurebase iframe to load.Javier
Jul 11, 2024
Hey folks, any news regarding this matter? I’ve noticed that the app used to download 1.1 MB whereas it is on the 1.6 MB mark these days.
It’s not getting better and it is impacting our user experience.
Do you have short-term plans to alleviate the load, or make the whole widget SSR?
Atiq Gauri
Mar 21, 2024
Does this needs to be enabled in widget intialization or it enabled by default?
Bruno H
Mar 21, 2024
This feature is not yet available, but we're planning to add an option to toggle it on once it is released.