Can build v4.2, but not v5.0...why not?

Questions
21

No - as you can see from my repro above, this issue affects anyone trying to use babylon in node (unless there are plans to full release 5.0 as not an es module)

Just my two cents, I don’t know the average makeup of Babylon users, perhaps very few try to run babylon in node

22

you could use the UMD version instead npm i babylonjs

23

oh cool, I didn’t realise there was a difference other than tree-shaking

I guess shared code could selectively import based on an environment variable or something to get it working

1 Like