4.2.0-alpha.23 has been deployed and should address the issue
1 Like
alvov
22
@sebavan thank you very much! it works now 
1 Like
I’m getting the exact issue as described by @alvov in the npm install of babylon 4.2.0. Does anyone know if the fix for this made it passed alpha?