As the subject says, it has been a little while. The last time I subscribed to any BabylonJS package in any form, there were baked in examples that I found I had to isolate, and just package the important bits I actually needed/wanted in my application code. It was a little while ago, has that changed? Examples decoupled in other packages? Anything like that? Today, I’m not sure how I would subscribe, probably to the direct Node package, but I have not crossed that bridge yet. Thanks in advance for any insights.
Have you seen - How to get Babylon.js - Babylon.js Documentation
For me it is just adding a script tag for whatever I want included like this.
<script src="https://preview.babylonjs.com/babylon.js"></script>
<script src="https://preview.babylonjs.com/inspector/babylon.inspector.bundle.js"></script>
<script src="https://preview.babylonjs.com/loaders/babylonjs.loaders.min.js"></script>
<script src="https://preview.babylonjs.com/materialsLibrary/babylonjs.materials.min.js"></script>
<script src="https://preview.babylonjs.com/postProcessesLibrary/babylonjs.postProcess.min.js"></script>
<script src="https://preview.babylonjs.com/gui/babylon.gui.min.js"></script>
<script src="https://preview.babylonjs.com/proceduralTexturesLibrary/babylonjs.proceduralTextures.min.js"></script>
<script src="https://preview.babylonjs.com/serializers/babylonjs.serializers.min.js"></script>
<script src="https://preview.babylonjs.com/nodeEditor/babylon.nodeEditor.js"></script>
What are the important bits that you had to isolate?
1 Like
At the time I started with the NuGet package into an ASP.NET MVC context. But this resulted a bunch of demo-ware that were extraneous and unnecessary to what we were doing. I ended up distilling a run-time bits package from that, essentially with only these sort of scripts included. Today, I would start from node npm packages more than likely. In either case, so as to avert dependency on a third party web site that may or may not be able to resolve from our hosted context. I was just curious if that packaging issue was still there today?
Nope you should be all good by using our es6 packages on npm 
https://doc.babylonjs.com/features/es6_support
https://doc.babylonjs.com/features/npm_support