feat(FEC-8212): support modular build process

.babelrc

@@ -1,6 +1,18 @@
 {
   "presets": [
-    "es2015"
+    [
+      "env",
+      {
+        "modules": false,
+        "useBuiltIns": true,
+        "targets": {
+          "browsers": [
+            ">0.25%",
+            "not op_mini all"
+          ]
+        }
+      }
+    ]
   ],
   "ignore": [
     "node_modules/**/*"

.eslintignore

@@ -5,3 +5,4 @@ karma.conf.js
 webpack.config.js
 webpack.config.ovp.js
 webpack.config.ott.js
+src/cast/remote-player.js

.eslintrc

@@ -20,6 +20,7 @@
   "globals": {
     "should": true,
     "sinon": true,
+    "playkit": true,
     "__VERSION__": true,
     "__NAME__": true,
     "__PACKAGE_URL__": true,

.flowconfig

@@ -4,15 +4,8 @@
 [libs]
 ./src/index.js
 node_modules/@playkit-js/playkit-js/flow-typed/
-node_modules/@playkit-js/playkit-js-hls/flow-typed/
-node_modules/@playkit-js/playkit-js-dash/flow-typed/
 node_modules/@playkit-js/playkit-js-ui/flow-typed/
-node_modules/playkit-js-providers/flow-typed/
+node_modules/@playkit-js/core-provider/flow-typed/
+node_modules/@playkit-js/core-provider/src/
 [options]
 unsafe.enable_getters_and_setters=true
-module.name_mapper='playkit-js-providers' -> 'playkit-js-providers/dist/playkit-ovp-provider'
-module.name_mapper='playkit-js-providers' -> 'playkit-js-providers/dist/playkit-ott-provider'
-module.name_mapper='player-defaults' -> '<PROJECT_ROOT>/src/ovp/player-defaults'
-module.name_mapper='player-defaults' -> '<PROJECT_ROOT>/src/ott/player-defaults'
-module.name_mapper='poster' -> '<PROJECT_ROOT>/src/ovp/poster'
-module.name_mapper='poster' -> '<PROJECT_ROOT>/src/ott/poster'

.prettierignore

@@ -5,3 +5,4 @@ yarn.lock
 yarn-error.log
 LICENSE
 /samples
+src/common/cast/remote-player.js

docs/ads.md

@@ -59,7 +59,7 @@ if (player.ads.isAdBreak()) {
 ## Ad Events Timeline
 
 During ad playback, there are events that get triggered to indicate the current ad state or state changes.
-Some events are life cycle indicators and will always get triggered, while others are reactive to specific actions -- such as the user clicking the ad -- and may or may not be triggered.  
+Some events are life cycle indicators and will always get triggered, while others are reactive to specific actions -- such as the user clicking the ad -- and may or may not be triggered.
 
 In the following diagram you can observe the events timeline from the point that an ad break starts to the point that the ad break ends.
 
@@ -112,8 +112,8 @@ You can observe the following timeline diagram that simulates these events' exac
 > Fires when the ad manifest has been loaded and the ad layout is available.
 > <br><br>_payload parameters:_
 >
-> | Name               | Type            | Description                                                      |
-> | ------------------ | --------------- | ---------------------------------------------------------------- |
+> | Name               | Type            | Description                                                         |
+> | ------------------ | --------------- | ------------------------------------------------------------------- |
 > | `adBreaksPosition` | `Array<number>` | An array that represents the ad break's time on the media timeline. |
 
 #
@@ -123,8 +123,8 @@ You can observe the following timeline diagram that simulates these events' exac
 > Fires when an ad has been loaded and ad data is available.
 > <br><br>_payload parameters:_
 >
-> | Name | Type        | Description  |
-> | ---- | ----------- | ------------ |
+> | Name | Type        | Description |
+> | ---- | ----------- | ----------- |
 > | `ad` | [`Ad`](#Ad) | The ad data |
 
 #
@@ -134,8 +134,8 @@ You can observe the following timeline diagram that simulates these events' exac
 > Fires when an ad has been started and ad data is available.
 > <br><br>_payload parameters:_
 >
-> | Name | Type        | Description  |
-> | ---- | ----------- | ------------ |
+> | Name | Type        | Description |
+> | ---- | ----------- | ----------- |
 > | `ad` | [`Ad`](#Ad) | The ad data |
 
 #
@@ -177,9 +177,9 @@ You can observe the following timeline diagram that simulates these events' exac
 >
 > | Name       | Type     | Description                                                                 |
 > | ---------- | -------- | --------------------------------------------------------------------------- |
-> | `severity` | `string` | The error severity                                                    |
-> | `category` | `string` | The error category                                                        |
-> | `code`     | `number` | The error code                                                             |
+> | `severity` | `string` | The error severity                                                          |
+> | `category` | `string` | The error category                                                          |
+> | `code`     | `number` | The error code                                                              |
 > | `data`     | `Object` | The error data: the original ad error can be accessed by `data.innerError`. |
 
 #
@@ -195,8 +195,8 @@ You can observe the following timeline diagram that simulates these events' exac
 > Fires before an ad break is about to start.
 > <br><br>_payload parameters:_
 >
-> | Name      | Type                  | Description        |
-> | --------- | --------------------- | ------------------ |
+> | Name      | Type                  | Description       |
+> | --------- | --------------------- | ----------------- |
 > | `adBreaK` | [`AdBreak`](#AdBreak) | The ad break data |
 
 #
@@ -248,8 +248,8 @@ You can observe the following timeline diagram that simulates these events' exac
 > Fires on ad time progress.
 > <br><br>_payload parameters:_
 >
-> | Name         | Type               | Description           |
-> | ------------ | ------------------ | --------------------- |
+> | Name         | Type               | Description          |
+> | ------------ | ------------------ | -------------------- |
 > | `adProgress` | `AdProgressObject` | The ad progress data |
 >
 > ###### Type `AdProgressObject`