Enable strict type checking

[lukasIO]

This also fixes all errors that showed up and paves the way for more ergonomic usage by upgrading protobuf-es to v2.x (once the protovalidate types are available )

[changeset-bot]

🦋 Changeset detected

Latest commit: ebcfafc

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 6 packages

Name	Type
@livekit/rtc-node	Patch
@livekit/rtc-node-darwin-arm64	Patch
@livekit/rtc-node-darwin-x64	Patch
@livekit/rtc-node-linux-arm64-gnu	Patch
@livekit/rtc-node-linux-x64-gnu	Patch
@livekit/rtc-node-win32-x64-msvc	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[bcherry]

@lukasIO does this actually work for you? There aren't any automated tests on livekit-rtc, so the green check is misleading, but all of the examples fail due to issues with missing required fields at serialization as described in this issue (that I see you're already active in!)

I think we might need to roll this back...

file:///Users/ben/dev/livekit/node-sdks/node_modules/.pnpm/@[email protected]/node_modules/@bufbuild/protobuf/dist/esm/to-binary.js:34
                throw new Error(`cannot encode field ${msg.desc.typeName}.${f.name} to binary: required field not set`);
                      ^

Error: cannot encode field livekit.proto.RoomOptions.adaptive_stream to binary: required field not set
    at writeFields (file:///Users/ben/dev/livekit/node-sdks/node_modules/.pnpm/@[email protected]/node_modules/@bufbuild/protobuf/dist/esm/to-binary.js:34:23)
    at writeMessageField (file:///Users/ben/dev/livekit/node-sdks/node_modules/.pnpm/@[email protected]/node_modules/@bufbuild/protobuf/dist/esm/to-binary.js:78:9)
    at writeField (file:///Users/ben/dev/livekit/node-sdks/node_modules/.pnpm/@[email protected]/node_modules/@bufbuild/protobuf/dist/esm/to-binary.js:61:13)
    at writeFields (file:///Users/ben/dev/livekit/node-sdks/node_modules/.pnpm/@[email protected]/node_modules/@bufbuild/protobuf/dist/esm/to-binary.js:38:9)
    at writeMessageField (file:///Users/ben/dev/livekit/node-sdks/node_modules/.pnpm/@[email protected]/node_modules/@bufbuild/protobuf/dist/esm/to-binary.js:78:9)
    at writeField (file:///Users/ben/dev/livekit/node-sdks/node_modules/.pnpm/@[email protected]/node_modules/@bufbuild/protobuf/dist/esm/to-binary.js:61:13)
    at writeFields (file:///Users/ben/dev/livekit/node-sdks/node_modules/.pnpm/@[email protected]/node_modules/@bufbuild/protobuf/dist/esm/to-binary.js:38:9)
    at toBinary (file:///Users/ben/dev/livekit/node-sdks/node_modules/.pnpm/@[email protected]/node_modules/@bufbuild/protobuf/dist/esm/to-binary.js:27:12)
    at FfiClient.request (/Users/ben/dev/livekit/node-sdks/packages/livekit-rtc/src/ffi_client.ts:56:22)
    at Room.connect (/Users/ben/dev/livekit/node-sdks/packages/livekit-rtc/src/room.ts:133:36)

Node.js v20.16.0

[lukasIO]

runtime errors 😬

will open a PR to rollback and work on fixing these.
The error you are running into is a type mismatch between manually constructed types and internal ffi types, glad we're running into these issues now instead of silently swallowing them. It basically means the change is working as intended, but I glanced over the runtime error possibility.

I'd prefer to merge #310 instead of the rollback, but the lack of exhaustive tests makes this slightly higher risk.