Lite is improving rapidly, and I’m often trying to determine if a particular change has been released. I couldn’t find evidence that a new package version results in a commit to the Babylon-lite repo. That’s typically where I’d look to see if the change I want is available. Is there a better way? Thanks!
cc @RaananW
Hi! Yes. npm records the exact source commit for each published version. For example:
npm view @babylonjs/lite@1.29.0 gitHead
The result is the commit ID for that package. Each release also has a tag such as npm-lite-v1.29.0. The GitHub release page has a Full Changelog link that compares it with the previous release. That is the easiest way to see which commits were included.
This is clearly something I should have already known about npm packages. Thank you for the explanation!