Replacement to MediaStreamError
See original GitHub issueWhat is this issue about?
This issue Is about the removal of MediaStreamError
in typescript 4.4, as mentioned in https://github.com/microsoft/TypeScript-DOM-lib-generator/issues/1029. Since the file path https://github.com/basst314/ngx-webcam/blob/master/src/app/modules/webcam/domain/webcam-init-error.ts#L3.
Do look into the issue asap. Waiting for a reply.
Thanks!
Issue Analytics
- State:
- Created 2 years ago
- Comments:14 (1 by maintainers)
Top Results From Across the Web
143335 – WebRTC: Replace NavigatorUserMediaError with ...
Align with the Media Capture and Streams specification. NavigatorUserMediaError is out and MediaStreamError [1] is its replacement.
Read more >Getting MediaStreamError { name: "AbortError", message ...
My desktop PC camera is Logitech (Logitech HD WebCam C270), and I saw on another post for the same error Firefox 54 (ubuntu...
Read more >Navigator.getUserMedia() - Web APIs | MDN
When the call fails, the function specified in the errorCallback is invoked with a MediaStreamError object as its sole argument; ...
Read more >Media Capture and Streams - W3C on GitHub
This is a draft document and may be updated, replaced or obsoleted by ... If the MediaStreamError event named overconstrained is thrown, ...
Read more >web_sys::MediaStreamError - Rust - Docs.rs
Getter for the name field of this object. MDN Documentation. This API requires the following crate features to be activated: MediaStreamError ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@ChrisLoes as a quick fix I added this to my typings.d.ts global types file.
+1. This comes up as an issue with Angular 13 now.