Hi,
While testing ladybugdb with TypeScript and Node.js, I noticed that the documentation always references imports from @ladybugdb/core. However, the actual lbugjs.node binary is located in a subpackage (e.g., @ladybugdb/core-win32-x64). This causes a "module not found" error (see native.js line 13 for ref).
If I import directly from the subpackage (e.g., @ladybugdb/core-win32-x64), the types property is missing in the subpackage’s package.json. This field is not copied from the root package.json (Ref), which breaks TypeScript support.
I’m happy to submit a PR to fix this, but I’d like to align on the preferred approach first.
Let me know how you’d like to proceed!
Hi,
While testing ladybugdb with TypeScript and Node.js, I noticed that the documentation always references imports from @ladybugdb/core. However, the actual lbugjs.node binary is located in a subpackage (e.g., @ladybugdb/core-win32-x64). This causes a "module not found" error (see native.js line 13 for ref).
If I import directly from the subpackage (e.g., @ladybugdb/core-win32-x64), the types property is missing in the subpackage’s package.json. This field is not copied from the root package.json (Ref), which breaks TypeScript support.
I’m happy to submit a PR to fix this, but I’d like to align on the preferred approach first.
Let me know how you’d like to proceed!