Runtime errors with inspector and serializers when using my own BJS forked repo

Hi all. Im getting some runtime errors with inspector and serializer when using my own forked BJS repo . This is how I have package.json set up


  "dependencies": {
  "@babylonjs/core": "git+https://github.com/myrepo/Babylon.js.git#master:packages/dev/core",
  "@babylonjs/gui": "git+https://github.com/myrepo/Babylon.js.git#master:packages/dev/gui",
  "@babylonjs/gui-editor": "git+https://github.com/myrepo/Babylon.js.git#master:packages/dev/guiEditor",
  "@babylonjs/inspector": "git+https://github.com/myrepo/Babylon.js.git#master:packages/dev/inspector",
  "@babylonjs/loaders": "git+https://github.com/myrepo/Babylon.js.git#master:packages/dev/loaders",
  "@babylonjs/materials": "git+https://github.com/myrepo/Babylon.js.git#master:packages/dev/materials",
  "@babylonjs/serializers": "git+https://github.com/myrepo/Babylon.js.git#master:packages/dev/serializers",  
  }

the error im getting is:

 The plugin "vite:dep-scan" was triggered by this import

    src/renderer/exporters/gltfExport.js:2:28:
      2 │ import { GLTF2Export } from '@babylonjs/serializers';
        ╵                             ~~~~~~~~~~~~~~~~~~~~~~~~

  The plugin "vite:dep-scan" was triggered by this import

    src/renderer/utils/showInspector.js:3:7:
      3 │ import "@babylonjs/inspector";
        ╵        ~~~~~~~~~~~~~~~~~~~~~~

normally this happens when vite cant find the packages. What am I missing? I verified these packages do exist in git.
eg: Babylon.js/tree/master/packages/dev/serializers

now sure how well these dependency-references work TBH. why not use npm link on the compiled public packages?

It’s documented here, but since you are using most packages, it would be the best to just run npm run build:es6, wait for it to be done, and then run npm link on the packages you want to use.

ah ya, i just saw the bit about npm link via the docs. This is a case of read the manual first before asking questions. I’ll report back if I have issues.

2 Likes