Thanks — I see you're reporting that

livekit_client >= 2.6.2

is incompatible with

livekit_components >= 1.2.3

. I can help diagnose and suggest next steps, but I need a bit more detail to pinpoint the root cause. Could you share the following: 1. The exact error message(s) you see (build-time, install-time, or runtime). 2. Your package/dependency list (package.json or the output of

npm ls livekit-client livekit-components

/

yarn list

/

pnpm list

). 3. Where the incompatibility shows up (during install, during bundling, when running the app, or when using a specific component/API). 4. The environment: Node/npm/yarn/pnpm versions, bundler (webpack/Vite/parcel), and the target (browser, React Native, etc.). 5. If possible, a minimal reproduction repo or the smallest code snippet that triggers the issue. While you gather that, a few quick things to check that commonly cause this type of version mismatch: • Ensure you don’t have multiple versions of

livekit-client

installed (one top-level and one nested). Run

npm ls livekit-client

to confirm. Multiple copies can cause runtime type/instance mismatches. • Confirm `livekit_components`'s peer dependency requirement for the

livekit-client

major version. Example apps typically use matching major versions of both packages; mismatched major versions can break internal APIs. • If you use a bundler, ensure package resolution doesn’t alias or bundle different copies of the client (some bundlers can duplicate dependencies). • If you see API/typing errors only in TypeScript, check that your TS config isn’t pulling incompatible type definitions from different versions. Tell me the details above and I’ll recommend the exact resolution steps (specific package versions to align, how to force a single client copy, or a code workaround). Sources: client-sdk-js | livekit/livekit_composite | DeepWiki