I tried installing npm install babylonjs-gltf2interface@8.11.0, Then there was an error.
I noticed that version 8.11.0 is already included on npm
I’m not sure why, but npm install @ babylonjs/ core@8.11.0 It’s normal.
There are other issues as well：
cc @sebavan
cc @ryantrem / @AlitarSemiramis who own the build while Raanan is out
Looking…
I’m not able to repro this, but I’ve seen cases in the past where the npmjs.org frontend shows a package version before it is actually available from the feed, so I’m guessing you just caught this almost immediately after the latest package was pushed to npmjs.
I’m not able to repro either. @ryantrem’s theory seems plausible.
It’s strange, I still can’t install it now babylonjs-gltf2interface@8.11.0 And @ babylonjs/ gui-editor@8.11.0
Even when I installed it with pnpm, it still reported an error.
I used pnpm view babylonjs-gltf2interface versions to check the latest version.
The version list is as follows:
So I didn’t see the 8.11.0 version of babylonjs-gltf2interface
It seems you are using a mirror/proxy registry (https://registry.npmmirror.com) that is caching the previous version. If you execute the command:
npm dist-tag ls babylonjs-gltf2interface
you will get latest: 8.10.0 instead of the real latest version latest: 8.11.0.
If you want to maintain the mirror/proxy registry, you can resolve only your dependency by official Npm registry (up-to-date to latest version) in this way:
npm install babylonjs-gltf2interface --registry=https://registry.npmjs.org/
Otherwise you can set the official Npm registry as default:
npm config set registry https://registry.npmjs.org/
and then install the dependencies in the classic way.
yes， Your eyes are very sharp, pointing out the problem at once. It is indeed an https://registry.npmmirror.com error issue. Thank you
Thanks a lot !!!
