No way to use web-ifc-three with latest threejs version or any version other then 0.135.0

[brutestack]

Since this commit 852970e1137c9b1bdf189b4fe7deaf785408d47f there is no way to use web-ifc-three with any version of threejs other then 0.135.0 because of exact version match requirement in peerDependencies part of package.json

Is it really important for web-ifc-three to be used exactly with threejs version 0.135.0?

[HassanEmam]

You can build the package on your local machine and update dependency to Three.js version you need and use it in your project. I have tested it and it did work.

[makc]

@brutestack there is always a way ;)

[aka-blackboots]

@brutestack, I hope the fix by @makc worked. Let us know if it still does not work.

[brutestack]

@aka-blackboots , @makc thank you for your work. Unfortunately, web-ifc-three version 0.0.121 still has this issue.

Doing npm i gives me the following:

I have the following dependencies in my project:

The only way for me to get through this with latest versions of three and web-ifc-three is adding overrides section to my package.json like this (as @makc adviced):

"overrides": {
    "three": "0.146.0"
  },

[agviegas]

Hey, I just published a new version that uses 0.149.0! If neither this nor the solutions above solve your issue, let us know. Otherwise, we'll close this issue.

[DoisKoh]

This is still an issue, and the problem is that ThreeJS versions start at 0.X.X. It's probably better to just remove three as a peerDepedency until ThreeJS decides to increment the Major.

[makc]

until ThreeJS decides to increment the Major

which is likely never

[agviegas]

@DoisKoh how would you like to find the dependency in the library? 🤔

[DoisKoh]

Unfortunately I can't think of a solution outside of stating clearly in the documentation what version of ThreeJS is supported - as it stands right now, without manually modifying the package-lock.json, we can't install web-ifc-three due to the conflict in the peerDepedency version of ThreeJS and the actual newer versions of ThreeJS (because of npm's semver rules for anything below 0.X.X).