-
Notifications
You must be signed in to change notification settings - Fork 166
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
livekit-client 1.14.0 broken in Angular app #893
Comments
Hi, could you post the exact error message you get? It can't be the same as in #166 because we have since replaced the protobuf library that imported those paths. |
Ouch, I just realized that the first error is actually happening when adding |
had a closer look at this. Solving it differently without breaking backwards compatibility seems tricky. |
Well, that solution is pretty much the same as I described in my Additional Information section in my first comment:
Basically changing the way file |
It's not the same, as it will keep the actual type information. Did you confirm that |
I have confirmed that replacing |
nice, thanks! would you want to open a PR for it? |
Sure. I've already opened this one for a typo fix in the documentation, so I'm familiar with the process 😃 |
closed via #901 |
Describe the bug
What I'm expecting
Adding
livekit-client: 1.14.0
dependency to an Angular 16 project should work fine.What happens instead
Compilation of Angular 16 app (
ng build
) fails with the following errorWhich seems related to the track-processors API.
Reproduction
The error is easily replicable with the following steps:
Logs
System Info
Severity
blocking all usage of LiveKit
Additional Information
There is a way of fixing the issue manually, which is making an import in file
node_modules/livekit-client/dist/src/room/track/LocalAudioTrack.d.ts
:And replacing
<typeof this.kind>
with<TrackKind.Track.Kind>
in line node_modules/livekit-client/dist/src/room/track/LocalAudioTrack.d.ts:24:51But of course this is far from ideal.
The text was updated successfully, but these errors were encountered: