-
Notifications
You must be signed in to change notification settings - Fork 232
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No matching export in "node_modules/three/build/three.modules.js" for import "RGBFormat" #196
Comments
I have the same error. I just started clean Vite + VUE webpage. Also when installing ifc-web-viewer there was earlier error: I had to run |
I've been going inside the actual |
You seem to be right I think, here is a discussion that mentions that: https://discourse.threejs.org/t/attempted-import-error-rgbformat-is-not-exported-from-three-imported-as-rgbformat10/34230 So maybe the 'web-ifc-viewer' library should also be updated |
We'll update it today! |
Currently, I am using react-fiber in my project. The threejs version used in react-fiber is r139, while the threejs version used in web-ifc-viewer is r135. However, threejs version r137 has removed RGBFormat, which makes it impossible to build the project at the moment. I am unsure if the threejs version used in web-ifc-viewer has been upgraded. |
Hi @nhutruong-arent , it turns out that updating web-ifc-viewer to the latest three.js is not as easy as updating the dependency. It is likely that web-ifc-viewer will be substituted by components very soon, so we are unsure if spending time here is worth. We will publish the new documentation covering the new components API very soon this summer. Anyway, I have just merged a PR that should help with this issue. I'll publish a new version to npm now. |
@agviegas not sure if the version has been published or not since there is no new release on npmjs so far |
@quasarchimaere Sorry, my bad. Can you check again? It should be |
Using
web-ifc-viewer
with Vite + React + TS. After runningnpm run dev
I get this error.The text was updated successfully, but these errors were encountered: