Skip to content
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

Spec compliance? #375

Open
achingbrain opened this issue Mar 14, 2024 · 4 comments
Open

Spec compliance? #375

achingbrain opened this issue Mar 14, 2024 · 4 comments

Comments

@achingbrain
Copy link

achingbrain commented Mar 14, 2024

I'm trying to integrate this module with some isomorphic code that runs on node and in browsers but I've noticed some incompatibilities with the WebRTC types as supplied with TypeScript in lib.dom.d.ts.

These are just the errors tsc reported, there may be others.

@shinyoshiaki
Copy link
Owner

Spec compliance is planned in the roadmap, but no specific date has been set for when it will be implemented.
https://github.com/shinyoshiaki/werift-webrtc?tab=readme-ov-file#road-map-towards-20

@achingbrain
Copy link
Author

Sounds great. Would PRs that move this module closer to the spec be accepted?

@shinyoshiaki
Copy link
Owner

Acceptable, but be prepared to modify all existing test code if you are modifying an existing PeerConnection.
It may be easier to first implement a new PeerConnection with a different name like W3CPeerConnection

@ris-work
Copy link

It could be also in the form of a polyfill like https://github.com/murat-dogan/node-datachannel/tree/master/polyfill. It has been very helpful. I am just sharing ideas. These make life much easier as we can share the same code among multiple implementations (browser, wrtc-M87, wrtc-M94, libdatachannel).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants