# \[lite\] Is there a way to tell which commits are in a particular @babylon/lite package version?

**URL:** <https://forum.babylonjs.com/t/lite-is-there-a-way-to-tell-which-commits-are-in-a-particular-babylon-lite-package-version/64087>\
**Category:** Questions\
**Tags:** lite\
**Created:** [September 11, 2026, 7:24pm UTC](https://forum.babylonjs.com/t/lite-is-there-a-way-to-tell-which-commits-are-in-a-particular-babylon-lite-package-version/64087 "2026-09-11T19:24:42Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![ComicSans](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/comicsans/32/19314_2.png) [@ComicSans](https://forum.babylonjs.com/u/ComicSans)\
**Post date:** [September 11, 2026, 7:24pm UTC](https://forum.babylonjs.com/t/lite-is-there-a-way-to-tell-which-commits-are-in-a-particular-babylon-lite-package-version/64087/1 "2026-09-11T19:24:42Z")

</div>

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!

---

<div class="post-metadata">

**Author:** ![Deltakosh](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/deltakosh/32/26635_2.png) [@Deltakosh](https://forum.babylonjs.com/u/Deltakosh)\
**Post date:** [September 14, 2026, 2:29pm UTC](https://forum.babylonjs.com/t/lite-is-there-a-way-to-tell-which-commits-are-in-a-particular-babylon-lite-package-version/64087/2 "2026-09-14T14:29:04Z")

</div>

cc @RaananW

---

<div class="post-metadata">

**Author:** ![RaananW](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/raananw/32/28955_2.png) [@RaananW](https://forum.babylonjs.com/u/RaananW)\
**Post date:** [September 14, 2026, 2:59pm UTC](https://forum.babylonjs.com/t/lite-is-there-a-way-to-tell-which-commits-are-in-a-particular-babylon-lite-package-version/64087/3 "2026-09-14T14:59:21Z")

</div>

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](https://github.com/BabylonJS/Babylon-Lite/releases/tag/npm-lite-v1.29.0 "https://github.com/babylonjs/babylon-lite/releases/tag/npm-lite-v1.29.0") has a **Full Changelog** link that compares it with the previous release. That is the easiest way to see which commits were included.

---

<div class="post-metadata">

**Author:** ![ComicSans](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/comicsans/32/19314_2.png) [@ComicSans](https://forum.babylonjs.com/u/ComicSans)\
**Post date:** [September 14, 2026, 3:34pm UTC](https://forum.babylonjs.com/t/lite-is-there-a-way-to-tell-which-commits-are-in-a-particular-babylon-lite-package-version/64087/4 "2026-09-14T15:34:59Z")

</div>

This is clearly something I should have already known about npm packages. Thank you for the explanation!