[BUG] nodes/vectorstores/Chroma/core.ts(3,15): error TS2459: Module '"chromadb"' declares 'Collection' locally, but it is not exported.

[brookbnu]

Describe the bug
When attempting to build or run Flowise on Amazon Linux using pnpm build or pnpm dev, the process fails with TypeScript errors and lifecycle script failures. The same setup works perfectly on macOS. The TypeScript error indicates that the chromadb module declares Collection locally but does not export it. Additionally, the script in the server package fails with exit code 1 during startup.

To Reproduce
Steps to reproduce the behavior:

Clone the Flowise repository to an Amazon Linux environment.

Install dependencies using pnpm install.

Run pnpm dev or pnpm build.

Observe the following errors:

TypeScript error: nodes/vectorstores/Chroma/core.ts(3,15): error TS2459: Module '"chromadb"' declares 'Collection' locally, but it is not exported.

Lifecycle script start:default failed with exit code 1.

Expected behavior
The build and development processes (pnpm build and pnpm dev) should complete successfully without any TypeScript errors or lifecycle script failures, just as they do in a macOS environment.

Screenshots

Flow
N/A

Setup

Installation: pnpm install followed by pnpm dev

Flowise Version: 2.1.3

OS: Amazon Linux 2 (EC2 instance)

Node Version: 18.15.0

Browser: N/A (backend issue)

Additional context
The TypeScript build works on macOS but fails on Amazon Linux, suggesting a potential environment or dependency compatibility issue. Possible causes could include differences in Node.js versions, environment variables, architecture, or system dependencies. The chromadb module appears to have inconsistencies in its export structure, leading to TypeScript errors during the build. Additionally, the script in the server package (./run start) might have permission issues or incompatible dependencies in the Amazon Linux environment.

[brookbnu]

[brookbnu]

[brookbnu]

[YesIamZhen]

I found the same issue with Windows platform only, Mac works always well, are you the same?

[YesIamZhen]

My issue got fixed after I reclone it in a brand new folder. Try this.