engine_components icon indicating copy to clipboard operation
engine_components copied to clipboard

Build in angular is failing

Open armadinho opened this issue 1 year ago • 2 comments

Describe the bug 📝

I am using the components in angular 14.2.0 with typescript 4.7.2 and I cannot build the app.

The error i get is in 2 files:

  1. In file node_modules\openbim-components\src\navigation\PostproductionRenderer\src\postproduction.d.ts

Error: node_modules/openbim-components/src/navigation/PostproductionRenderer/src/postproduction.d.ts:15:39 - error TS2344: Type 'Event<string, unknown>' does not satisfy the constraint 'Object3DEventMap'. Type 'Event<string, unknown>' is missing the following properties from type 'Object3DEventMap': added, removed

15 excludedItems: Set<THREE.Object3D<THREE.Event>>;

  1. In file node_modules\openbim-components\src\core\SimpleRaycaster\index.d.ts

Error: node_modules/openbim-components/src/core/SimpleRaycaster/index.d.ts:33:216 - error TS2344: Type 'Event<string, unknown>' does not satisfy the constraint 'Object3DEventMap'. Type 'Event<string, unknown>' is missing the following properties from type 'Object3DEventMap': added, removed

33 castRayFromVector(origin: THREE.Vector3, direction: THREE.Vector3, items?: THREE.Mesh<THREE.BufferGeometry<THREE.NormalBufferAttributes>, THREE.Material | THREE.Material[]>[]): THREE.Intersection<THREE.Object3D<THREE.Event>> | null;

Reproduction ▶️

No response

Steps to reproduce 🔢

No response

System Info 💻

System:
    OS: Windows 11 10.0.22621
    CPU: (12) x64 11th Gen Intel(R) Core(TM) i5-11600K @ 3.90GHz
    Memory: 18.18 GB / 31.89 GB
  Browsers:
    Edge: Chromium (120.0.2210.144)
    Internet Explorer: 11.0.22621.1
  npmPackages:
    openbim-components: ^1.3.1 => 1.3.1

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.

armadinho avatar Jan 22 '24 13:01 armadinho

Which version of three and @types/three are you using?

HoyosJuan avatar Feb 02 '24 15:02 HoyosJuan

Hi @armadinho! Following up this issue, were you able to solve it?

HoyosJuan avatar Apr 11 '24 19:04 HoyosJuan

This should be solved with the latest version of the libraries. Closing this!

agviegas avatar Jun 20 '24 19:06 agviegas