Yup fix is in PR
It will be in the next nightly and npm
@sebavan I can confirm that that fix worked in production. Thank you!