Outdated three version

[tb-viktor]

Describe the bug 📝

Hey guys,

We're currently looking into upgrading from an old version of this library (before engine_components) to the latest one, and we're disappointed to see that the three version is still 0.160.1 - the same year old one that openbim-components used.

We don't use three exclusively to load IFC files, but also support other geometry types in our product, and for those running the newer versions of three is crucial because they contain important bug fixes. We ended up having to load two separate three versions in our package.json via aliases because of this, which was a temporary solution until we could migrate to engine_components and causes problems in other places.

Is there any work planned to upgrade the three version to the latest, or at least to 0.165.0 and higher?

Thanks!

Reproduction ▶️

No response

Steps to reproduce 🔢

Try to run the library with the latest three version.

System Info 💻

"@thatopen/components": "^2.4.4",

Used Package Manager 📦

npm

Error Trace/Logs 📃

No response

Validations ✅

• [x] Read the docs.
• [x] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• [x] Make sure this is a repository issue and not a framework-specific issue. For example, if it's a THREE.js related bug, it should likely be reported to mrdoob/threejs instead.
• [x] Check that this is a concrete bug. For Q&A join our Community.
• [x] The provided reproduction is a minimal reproducible example of the bug.

[cmcnicholas]

We are using latest version of three and very interested in the state of upgrading this repo, is there any particular area that needs help/research? for testing I have just --force'd my way through mismatching three version (because we use other three.js modules, it "seems" to work but I'm sure this is just survivor bias.

Fantastic job with these components by the way.

[cmcnicholas]

This could be closed now :)