Repository files navigation

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.

npm install webrtc-adapter

bower install webrtc-adapter

Just import adapter:

import adapter from 'webrtc-adapter';

No further action is required. You might want to use adapters browser detectionwhich 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.

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

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

You will findadapter.js inbower_components/webrtc-adapter/.

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 globaladapter object (window.adapter).
• adapter_no_global.js - same asadapter.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.

Head over totest/README.md and get started developing.

• 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 usepatch,minor ormajor in place of<version>. Runnpm 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 rungit pull
• Runnpm publish (you need access to thewebrtc-adapter npmjs package). For big changes, consider using atag version such asnext and thenchange 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.

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 usinggit checkout tags/vMajor.minor.patch.
• checkout a new branch, using a name such as patchrelease-major-minor-patch.
• cherry-pick the fixes usinggit cherry-pick some-commit-hash.
• runnpm version patch. This will create a new patch version and publish it on github.
• check outorigin/bumpVersion branch and publish the new version usingnpm 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.