Closed alexchuber closed 1 year ago
@CedricGuillemet This is because we are ignoring the lock file in the npm install function.
Yes, it's explicit in the command line to not use the package lock. Does it make sense to remove package lock in the repo?
Why not use the package lock file? Usually this is kind of an anti pattern since build behavior can change without making any changes to any files in the repo.
We should use the package lock file here. I added the ignoring of lock files for a different purpose for JsRuntimeHost.
Fixed with https://github.com/BabylonJS/BabylonNative/pull/1263 . closing.
If you run cmake at the time of writing, it will pull 6.11.2. But, if you run npm install, it will use 6.4.1.