npmpackage.info

Gathering detailed insights and metrics for webrtc-adapter

Other packages similar to webrtc-adapter

webrtc-adapter-test

0.2.10

Hide browser differences in WebRTC APIs (test package name)

rtc-everywhere

0.0.5

Cross-everything WebRTC Adapter/Polyfill

@teravoz/react-webrtc-adapter

0.11.0-beta

The Teravoz WebRTC Adapter for wrapping up your React componponents with telephonic capabilities

ortc-adapter

0.1.7

ORTC to WebRTC Adapter

Gathering detailed insights and metrics for webrtc-adapter

webrtc-adapter

Shim to insulate apps from spec changes and prefix differences. Latest adapter.js release:

9.0.1

3,637

BSD-3-Clause

JavaScript

63,348,551 6.4

Installations

npm install webrtc-adapter

Pull Requests

Open

2

Total

796

Closed

89

Merged

705

Issues

Open

7

Total

361

Closed

354

Releases

9.0.0

v9.0.0

Published on 27 Mar 2024

v8.0.0

Published on 06 May 2021

v7.2.5

Published on 07 Jul 2019

Fix issue with usage of this in addTrack/removeTrack shim

v7.1.1

Published on 11 Dec 2018

shim connectionState

v7.1.0

Published on 11 Dec 2018

ES6 all the things

v7.0.0

Published on 26 Nov 2018

View all 90 releases

Developer

webrtchacks

Developer Guide

BETA

Module System

CommonJS

Min. Node Version

>=6.0.0

Typescript Support

Yes

Node Version

20.12.0

NPM Version

10.5.0 Statistics

3,637 Stars

3,069 Commits

845 Forks

166 Watching

9 Branches

74 Contributors

Updated on 25 Nov 2024

Languages

JavaScript (99.92%)

HTML (0.08%)

Total Downloads

Cumulative downloads

Total Downloads

63,348,551

Last day

3.6%

91,854

Compared to previous day

Last week

5.4%

482,178

Compared to previous week

Last month

14.5%

1,976,002

Compared to previous month

Last year

15.9%

18,523,352

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Versions

WebRTC adapter

adapter.js is a shim to insulate apps from spec changes and prefix differences in WebRTC. The prefix differences are mostly gone these days but differences in behaviour between browsers remain.

This repository used to be part of the WebRTC organisation on github but moved. We aim to keep the old repository updated with new releases.

Install

NPM

1npm install webrtc-adapter

Bower

1bower install webrtc-adapter

Usage

Javascript

Just import adapter:

import adapter from 'webrtc-adapter';

No further action is required. You might want to use adapters browser detection which detects which webrtc quirks are required. You can look at

adapter.browserDetails.browser

for webrtc engine detection (which will for example detect Opera or the Chromium based Edge as 'chrome') and

adapter.browserDetails.version

for the version according to the user-agent string.

NPM

Copy to desired location in your src tree or use a minify/vulcanize tool (node_modules is usually not published with the code). See webrtc/samples repo as an example on how you can do this.

Prebuilt releases

Web

In the gh-pages branch prebuilt ready to use files can be downloaded/linked directly. Latest version can be found at https://webrtc.github.io/adapter/adapter-latest.js. Specific versions can be found at https://webrtc.github.io/adapter/adapter-N.N.N.js, e.g. https://webrtc.github.io/adapter/adapter-1.0.2.js.

Bower

You will find adapter.js in bower_components/webrtc-adapter/.

NPM

In node_modules/webrtc-adapter/out/ folder you will find 4 files:

adapter.js - includes all the shims and is visible in the browser under the global adapter object (window.adapter).
adapter_no_global.js - same as adapter.js but is not exposed/visible in the browser (you cannot call/interact with the shims in the browser).

Include the file that suits your need in your project.

Development

Head over to test/README.md and get started developing.

Publish a new version

Go to the adapter repository root directory
Make sure your repository is clean, i.e. no untracked files etc. Also check that you are on the master branch and have pulled the latest changes.
Depending on the impact of the release, either use patch, minor or major in place of <version>. Run npm version <version> -m 'bump to %s' and type in your password lots of times (setting up credential caching is probably a good idea).
Create and merge the PR if green in the GitHub web ui
Go to the releases tab in the GitHub web ui and edit the tag.
Add a summary of the recent commits in the tag summary and a link to the diff between the previous and current version in the description, example.
Go back to your checkout and run git pull
Run npm publish (you need access to the webrtc-adapter npmjs package). For big changes, consider using a tag version such as next and then change the dist-tag after testing.
Done! There should now be a new release published to NPM and the gh-pages branch.

Note: Currently only tested on Linux, not sure about Mac but will definitely not work on Windows.

Publish a hotfix patch versions

In some cases it may be necessary to do a patch version while there are significant changes changes on the master branch. To make a patch release,

checkout the latest git tag using git checkout tags/vMajor.minor.patch.
checkout a new branch, using a name such as patchrelease-major-minor-patch.
cherry-pick the fixes using git cherry-pick some-commit-hash.
run npm version patch. This will create a new patch version and publish it on github.
check out origin/bumpVersion branch and publish the new version using npm publish.
the branch can now safely be deleted. It is not necessary to merge it into the main branch since it only contains cherry-picked commits.

No vulnerabilities found.

10

Maintained

Determines if the project is "actively maintained".

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

License

Determines if the project has defined a license.

10

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

9

Pinned-Dependencies

Determines if the project has declared and pinned its dependencies.

6

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

5

Code-Review

Determines if the project requires code review before pull requests (aka merge requests) are merged.

0

CII-Best-Practices

Determines if the project has a CII Best Practices Badge.

0

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

0

Security-Policy

Determines if the project has published a security policy.

0

Fuzzing

Determines if the project uses fuzzing.

Score

6.4

/10

Last Scanned on 2022-08-15

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More

Other packages similar to webrtc-adapter

Other packages similar to webrtc-adapter

webrtc-adapter

Installations

Pull Requests

2

796

89

705

Issues

7

361

354

Releases

Developer

Developer Guide

CommonJS

>=6.0.0

Yes

20.12.0

10.5.0

Statistics

Languages

Total Downloads

63,348,551

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

Dev Dependencies

WebRTC adapter

Install

NPM

Bower

Usage

Javascript

NPM

Prebuilt releases

Web

Bower

NPM

Development

Publish a new version

Publish a hotfix patch versions

10

10

10

10

10

9

6

5

0

0

0

0

6.4

/10