Hi @Sean_Foo,
in the case of JS, this should be the workaround until we release the fix.
Thanks, Victor