webrtcHacks / adapter

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

Home Page:https://webrtcHacks.github.io/adapter/adapter-latest.js

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

look at version distribution

fippo opened this issue · comments

https://api.npmjs.org/versions/webrtc-adapter/last-week shows the download distribution. Looks like a considerable amount of 6.x usage

grabbing that data into s and then doing

majorVersions = {};
Object.keys(s.downloads).forEach(version => {
  const majorVersion = parseInt(version, 10);
  if (!majorVersions[majorVersion]) majorVersions[majorVersion] = 0;
  majorVersions[majorVersion] += s.downloads[version];
});

shows

Object { 0: 1, 1: 1615, 2: 2512, 3: 5898, 4: 1787, 5: 1046, 6: 25177, 7: 98195 }

So 20% of dependents are still stuck on version 6.

Object.keys(s.downloads).forEach(version => {
  const majorVersion = parseInt(version, 10);
  if (majorVersion < 6) return;
  console.log(version, s.downloads[version]);
})

at least mostly using the latest versions of 6 + 7

Object { 0: 14, 1: 3260, 2: 1958, 3: 4323, 4: 641, 5: 261, 6: 16590, 7: 119796, 8: 33792 }

Quite surprising 7.x is so popular given the big removal for 8.x was legacy Edge

Object { 0: 18, 1: 5263, 2: 1952, 3: 7406, 4: 610, 5: 566, 6: 49052, 7: 146731, 8: 51352 }

https://npmtrends.com/webrtc-adapter shows quite a large bump recently

Object {0: 10, 1: 7247, 2: 1491, 3: 4003, 4: 767, 5: 642, 6: 32823, 7: 190426, 8: 63210}

{0: 35, 1: 4334, 2: 891, 3: 2312, 4: 993, 5: 285, 6: 8877, 7: 112479, 8: 66910}
At least 6.x dropped in usage

{0: 3, 1: 30803, 2: 1342, 3: 2960, 4: 559, 5: 260, 6: 15729, 7: 133953, 8: 168522, 9: 7048}
v8 is slightly ahead now