engine_components
engine_components copied to clipboard
ThatOpen
Outdated three version causing problems with larger projects
Description 📝
Hello!
We're quite enthusiastic about using this library in our product, but we are encountering some issues while trying to set it up. We already use three separately from this library for a more generic 3D view, so there is a version conflict already when installing this library:
This can of course be solved by us downgrading our three version to the one this library uses, but we are not very happy with the idea of being locked out of bug fixes and updates because of it, and it also is a regressive change in terms of features and development time.
My question is - what is the maintenance strategy regarding this from your side? When can we expect three to be updated to a newer version? We understand it is not going to be immediately updated whenever a new version is there, we are also a bit behind, but aligning update cycles more closely would help us move forward with our integration.
Suggested solution 💡
Provide clarity and/or timeline in supporting new three versions
Alternative ⛕
No response
Additional context ☝️
No response
Validations ✅
- [X] Read the docs.
- [X] Check that there isn't already an issue that requests the same feature to avoid creating a duplicate.
@tb-viktor our plan is to update the three.js version with each release (the next one is in the start of January). Keep in mind though that our release calendar is not necessarily the same as the three.js release calendar, so there might always be an offset in the versions. That said, we have defined three.js as a peer dependency, so if there are no breaking changes, everything should work even with that offset
@tb-viktor our plan is to update the three.js version with each release (the next one is in the start of January). Keep in mind though that our release calendar is not necessarily the same as the three.js release calendar, so there might always be an offset in the versions. That said, we have defined three.js as a peer dependency, so if there are no breaking changes, everything should work even with that offset
@agviegas have you managed to make any progress with this? January is almost over and so far the version has not went up 🙂
Hey @tb-viktor sorry for the late reply. We are a super small team, so we had to leave the issues on stand by for some time. After a huge update, now we are addressing them all. Three is now a flexible peer dependency, so this shouldn't be a problem in the future. Let us know if you face this issue again. Thanks!