Yeah the “init repo” only makes sense on my station.
Currently, I work on three repos at the same time,
Nabu GitHub - SvenFrankson/nabu: Math functions for BabylonJS-based projects which are a few very simple tools I tend to use in many projects
Mummu GitHub - SvenFrankson/mummu: Generic functions for BabylonJS-based projects which contains everything related to Intersections and collisions
And Marble Run Simulator
What I do now, because I do many edits in Mummu while working on Marble Run Simulator, is that I have Symlinks pointing to Nabu and Mummu repo. This way I can seamlessly work on Mummu or Marble Run Simulator, then commit to both project separately.
I know that I could achieve that (maybe with less hassle concerning Symlink creation ^^) with a more standard build process, but
- I have low skills in theese domains
- Everytime I’ve tried to setup this kind of behavior, I eventually found it less efficient (might be because of the previous point ^^)
I’d take any hint about the standard way to do this with great pleasure ! But no need for a PR, it’s very likely it would collide with my homemade flow.
That being said, if you want to run it locally, you can !
- Clone project
- Add a “lib” folder
- With the following architecture
lib/
--mummu/
----mummu.d.ts
----mummu.js
--nabu/
----nabu.d.ts
----nabu.js
--babylon.js
--babylon.d.ts
--babylonjs.loaders.js
Mummu and Nabu files can be found at the GitHub links above.
Then tsc tsconfig.json should work.
(there’s a make_build.ps1 that I’ve written yestersday, it serves at copying only the runtime-relevant files when I want to update the online version)
(ok now that I’ve written the build process, I realize its sub-optimal when aiming at sharing it ^^)
Also reminds me of building coasters in rollercoaster tycoon 
I love it 
Here’s my design 
