I'm specifically interested in seeing the ClonerSystem published to @babylonjs/extensions/ClonerSystem && babylonjs-extension-cloner-system (preferably the first, if I had to pick one)
Though the Typescript .d.ts file should exclude the Demoscene class and should extend the BABYLON module, not create a new module (BABYLONX).
It would probably be good to add a package.json that defines @babylonjs/core as a (peer?) dependency at a specific version.
Ideally, all of the extensions would be published in this manner.
I'm specifically interested in seeing the ClonerSystem published to
@babylonjs/extensions/ClonerSystem
&&babylonjs-extension-cloner-system
(preferably the first, if I had to pick one)Though the Typescript
.d.ts
file should exclude theDemoscene
class and should extend theBABYLON
module, not create a new module (BABYLONX
).It would probably be good to add a
package.json
that defines@babylonjs/core
as a (peer?) dependency at a specific version.Ideally, all of the extensions would be published in this manner.