IFC code is almost a year old

[wwwouter]

Description

The IFC files (https://github.com/mrdoob/three.js/tree/dev/examples/jsm/loaders/ifc) are from Feb 18th and since then there have been many updates

For a while I downloaded the web-ifc and IFCLoader files and updated the imports myself. But with every update of Three.js and/or IFC.js this would break. Therefore I chose just to rely on the Three.js repository for the loader and all other IFC dependencies.

Here is mentioned that the IFC dependencies will probably move outside of this repository (https://github.com/mrdoob/three.js/pull/25057/files#r1037975491), but I can't see any changes just yet.

Is it possible to update the IFC dependencies for now, while we wait for the new way of importing dependencies for "external" examples?

For me it would be better if there was a stand-alone IFCLoader package on npm, with all the correct dependencies linked. Is that something has been considered before?

Reproduction steps

Code

// code goes here

Live example

• jsfiddle-latest-release
• jsfiddle-dev

Screenshots

No response

Version

148

Device

No response

Browser

No response

OS

No response

[mrdoob]

/ping @agviegas

[agviegas]

Woops, sorry. These weeks have been really bloated. As mentioned here, I will update the example to import the loader from here using importmaps and unpkg. Is this correct? If so, I will start working on this today.

[mrdoob]

@agviegas That is correct 👍

[wwwouter]

Ok, then I'll wait for this update.

I see that because of ThatOpen/web-ifc-three#115 I need to use --legacy-peer-deps, because I'm on a recent version of Three.js

Also when I just update the import like stated here https://ifcjs.github.io/info/docs/Guide/web-ifc-three/Introduction#can-i-use-the-threeifcloader-directly, I get this error

But that's probably not something that should be reported here.

[agviegas]

@mrdoob understood, I will get hands-on with this right away. Sorry for the delay and thanks again!