# \[Solved\] Version difference for es6 and standard library **URL:** \ **Category:** Questions\ **Created:** [February 27, 2019, 2:08pm UTC](https://forum.babylonjs.com/t/solved-version-difference-for-es6-and-standard-library/1635 "2019-02-27T14:08:28Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Hersir](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/hersir/32/108_2.png) [@Hersir](https://forum.babylonjs.com/u/Hersir)\ **Post date:** [February 27, 2019, 2:08pm UTC](https://forum.babylonjs.com/t/solved-version-difference-for-es6-and-standard-library/1635/1 "2019-02-27T14:08:29Z")
Hi, would like to know if es6 version is synced with standard `babylonjs` on npm. I see that standard one have version `alpha29`, but es6 `alpha18` , (alpha17 after install). this is temporal or there will be version differences in future as well ? Thank you ---
**Author:** ![sebavan](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/sebavan/32/57_2.png) [@sebavan](https://forum.babylonjs.com/u/sebavan)\ **Post date:** [February 27, 2019, 2:46pm UTC](https://forum.babylonjs.com/t/solved-version-difference-for-es6-and-standard-library/1635/2 "2019-02-27T14:46:48Z")
They are the same version if you install from @preview 17 was the first npm release (published as preview) but npm wanted at least one stable and they picked the first one ๐Ÿ™‚ The build/publish process is always done at the same time to prevent any confusion. ---
**Author:** ![Leon](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/leon/32/30387_2.png) [@Leon](https://forum.babylonjs.com/u/Leon)\ **Post date:** [February 27, 2019, 3:15pm UTC](https://forum.babylonjs.com/t/solved-version-difference-for-es6-and-standard-library/1635/3 "2019-02-27T15:15:26Z")
I still thing we should release the latest preview as @latest also, since people getting started with the new @babylonjs/\* will probably install it without adding the tag. Then when we release 4.0.0 we can start using @latest - stable release with semver @next - a beta or alpha but a โ€œstableโ€ version @nightly - could be in an instable state, but should could be built and published by a CI How do we publish to npm today? CI based? Script based? Iโ€™ll help out if you want ๐Ÿ™‚ ---
**Author:** ![Hersir](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/hersir/32/108_2.png) [@Hersir](https://forum.babylonjs.com/u/Hersir)\ **Post date:** [February 28, 2019, 8:12am UTC](https://forum.babylonjs.com/t/solved-version-difference-for-es6-and-standard-library/1635/4 "2019-02-28T08:12:32Z")
@sebavan thanks. yes installed wrong version ๐Ÿ™‚ ---
**Author:** ![sebavan](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/sebavan/32/57_2.png) [@sebavan](https://forum.babylonjs.com/u/sebavan)\ **Post date:** [February 28, 2019, 6:57pm UTC](https://forum.babylonjs.com/t/solved-version-difference-for-es6-and-standard-library/1635/5 "2019-02-28T18:57:19Z")
It is all script based and easy to put it in CI. We do prefer to still manually run the script to limit the number of release on npm without nightly. We ll push a @latest in bit as I agree this is confusing as long as the first stable as not been released.