Experimental StreamAMG support and build tooling

Author: driskell

.github/workflows/publish.yml

@@ -0,0 +1,24 @@
+name: Publish package to GitHub Packages
+on:
+  release:
+    types:
+    - created
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      packages: write
+    steps:
+      - uses: actions/checkout@v3
+      # Setup .npmrc file to publish to GitHub Packages
+      - uses: actions/setup-node@v3
+        with:
+          node-version: 14
+          cache: yarn
+          cache-dependency-path: yarn.lock
+      - run: yarn ci
+      - run: yarn publish
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.nvmrc

@@ -0,0 +1 @@
+@othermedia:registry=https://npm.pkg.github.com

.vscode/settings.json

@@ -0,0 +1,6 @@
+// Added by OM
+{
+    "typescript.validate.enable": false,
+    "javascript.validate.enable": false,
+    "markdown.extension.toc.updateOnSave": false
+}

OMREADME.md

@@ -0,0 +1,20 @@
+# `playkit-js-providers`
+
+Because the upstream player utilises API v3.3.0 and StreamAMG do not support it yet (they're on v3.1.6) a provider replacement is needed. The main differences between the two API versions are as follows:
+
+- v3.3.0 has a baseEntry.getPlaybackContext API that returns access control information and playback sources. This does not exist in v3.1.6. Instead, the access control information is loaded via baseEntry.getContextData and is exactly the same response format as v3.3.0's getPlaybackContext except it has no sources or bumper data. We can ignore bumper data, and simply hard-code in a playManifest URL in any custom provider we build.
+- v3.3.0 thumbnail requests seem to be slightly different slicing to what v3.1.6 provides - however, it is possible that StreamAMG have changed their thumbnail responses for their own implementation in their current IFRAME player. So some adjustments are needed if the thumbnail on the scrubber is needed.
+- v3.3.0 allows POST requests with a JSON body. v3.1.6 only supports GET requests with the request information specified as query parameters, or a POST request with form data. Therefore a custom provider will need to use that request format. The response format however, is fortunately, the same.
+
+## StreamAMG Provider
+
+This fork mainly adds a new [StreamAMG Provider](src/k-provider/streamamg). It extends the OVP provider which is for Kaltura API v3.3.0 and implements the necessary overrides and extensions to support API v3.1.6, with all of the above differences resolved.
+
+## Additional Changes
+
+- Added `.vscode` to suppress TypeScript and ESLint checks since this is using Flow. You'll likely want to install Flow extension for VSCode.
+- Adjusted `src/index.html` that now has StreamAMG endpoints in there for testing.
+
+## Building and Testing
+
+See the main [README](README.md) file for information.

README.md

@@ -1,3 +1,7 @@
+# OTHER MEDIA FORK
+
+See [OMREADME.md](OMREADME.md)
+
 # PlayKit JS Providers - Cloud TV and OVP Media Provider Plugins for the [PlayKit JS Player]
 
 [![Build Status](https://travis-ci.com/kaltura/playkit-js-providers.svg?token=s2ZQw18ukx9Q6ePzDX3F&branch=master)](https://travis-ci.com/kaltura/playkit-js-providers)