You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am bit confused with the state of the branches/tags/releases. There is no git tag for 3.4.3, so I don't know from what git commit it was released. There is a git branch 3.4.x that still uses Float32Array, but there is a tag for 3.4.1 which does contain IndexedCollection, but was not released to npm.
So my questions are, where was 3.4.3 released from? and would be it possible to get a released with the IndexedCollection changes included?
In the meantime, I have a patch applied to adjust the types locally, so it is not a big deal if this cannot happen for backward compatibility or other reasons.
Thanks!
The text was updated successfully, but these errors were encountered:
Just wanted to check if there’s a chance to get a patch release (v3.4.4) with the updated TypeScript typings. It would save developers from maintaining local patches 🙏
I noticed the change from
Float32Array
in the types toIndexedCollection
and I needed to use this for my current project.I am using the latest release on npm
3.4.3
, but there the type is stillFloat32Array
:https://www.npmjs.com/package/gl-matrix?activeTab=code
I am bit confused with the state of the branches/tags/releases. There is no git tag for
3.4.3
, so I don't know from what git commit it was released. There is a git branch3.4.x
that still uses Float32Array, but there is a tag for3.4.1
which does containIndexedCollection
, but was not released to npm.https://github.com/toji/gl-matrix/blob/v3.4.1/src/types.d.ts
So my questions are, where was 3.4.3 released from? and would be it possible to get a released with the
IndexedCollection
changes included?In the meantime, I have a patch applied to adjust the types locally, so it is not a big deal if this cannot happen for backward compatibility or other reasons.
Thanks!
The text was updated successfully, but these errors were encountered: