chore(types): use 'import type' for type-only imports in SDK

[lightning-sagar]

Summary

This PR fixes incorrect type imports in the @stream-io/video-react-sdk.
All type-only imports now use import type instead of a regular import, following TypeScript best practices.

Changes

• Updated type imports in SDK source files

Why

• Ensures types are correctly stripped from compiled JavaScript
• Improves compatibility with bundlers (Vite, Next.js)
• Aligns with TypeScript best practices

Closes #1928

[oliverlaz]

hi @lightning-sagar, thank you for your effort and contribution. Before moving forward I'd like to ask you sign this CLA:

• https://docs.google.com/forms/d/e/1FAIpQLScFKsKkAJI7mhCr7K9rEIOpqIDThrWxuvxnwUq2XkHyG154vQ/viewform

Afterwards, to make this future-prone and performant, can you please update our TS config files and enable the verbatimModuleSyntax?

• https://www.typescriptlang.org/tsconfig/#verbatimModuleSyntax

I expect yarn build:all to start failing for other packages, but once everything is green, we can move forward and accept this PR.

[lightning-sagar]

Hi @oliverlaz, I’ve addressed the changes you requested... however, after running yarn build:all, there are a lot of unused variable warnings across the SDK... should I leave them as is for now? as for now it didn't block the build.

[lightning-sagar]

Hi @oliverlaz , I’ve pushed the latest changes,everything is now updated as requested...
I ran yarn build:all and it passes successfully without failures.

⚠️ There are still warnings about unused variables/components across the packags, but they don’t block or break the build...

[oliverlaz]

hey @lightning-sagar, I don't expect to see "unused variables" issues. Can you please share a sample output here?

[lightning-sagar]

hi @oliverlaz , sorry for the earlier confusion! just to clarify, the warnings I mentioned are related to unused external imports (e.g., Observable, Subject from rxjs, and UnaryCall from @protobuf-ts/runtime-rpc) these are showing up during the build but dont block or break it...

✅ I’ve completed all requested changes:

• Updated all type-only imports to use import type
• Enabled verbatimModuleSyntax in the TS config
• Ran yarn build:all, all packages build successfully with no errors...

is there anything else you'd like me to address, or are we good to proceed with the review/approval???

[lightning-sagar]

hi @oliverlaz ,
I’ve made all the requested changes (type-only imports, verbatimModuleSyntax, and confirmed yarn build:all passes)
Is the PR ready for approval, or would you like me to address anything else?

Thanks!

[oliverlaz]

Hi @lightning-sagar, thanks for your contributions.
I'll review this PR in more detail later this week, and if everything is good, I'll go ahead and merge it.

[oliverlaz]

hi @lightning-sagar, do you mind solving the remaining conflicts before we continue merging your contribution?

[oliverlaz]

Hi @lightning-sagar, apologies for the late answers.
This PR got stale and has lots of conflicts that I can't resolve, as I'm not the owner of it.

Would you like to update it and then quickly merge it? One important thing to note is, there shouldn't be any changes in the lock file too.

[lightning-sagar]

hi @oliverlaz , sorry for the trouble earlier. at that time i wasnt very familiar with open source workflow and pr hygiene, and i realize it caused extra work for you...
over the last few months i have learned a lot from contributing more actively, also i have now resolved the conflicts and updated the pr accordingly. thanks.

[lightning-sagar]

@oliverlaz are these ci failures related to this pr? a few seem to be failing due to missing .env/secrets, others are lint related (they pass locally for me), and the pr title check that you have already fixed..

[oliverlaz]

hi @lightning-sagar, the CI failures are caused by our linters.
Can you run yarn lint:all on your side and push the changes?

[lightning-sagar]

@oliverlaz ,i ran yarn lint:all locally, there was no logic lint errors.. the failures are due to prettier formatting being off in a lot of files. this will result in a large number of formatting only changes, which i will fix and push shortly