Moving to node_modules folder to make easier to upgrade

trying to move from Bootstrap 3 to Bootstrap 5

node_modules/videojs-contrib-ads/docs/integrator/migration-guides/migrating-to-2.0.md

@@ -0,0 +1,24 @@
+# Guidance for Ad Plugin Maintainers
+One of the best features of video.js is the community of plugins and customizations that has built up around it.
+Ad support is an important part of that ecosystem but not all plugin authors write with advertisements in mind (and we probably won't be able to convince them to start).
+Rather than throw our hands in the air, we're making some big changes in [videojs-contrib-ads](https://github.com/videojs/videojs-contrib-ads) to make advertisements more compatible with the rest of the video.js universe.
+In version 2.0 of the plugin, we redispatch events with different prefixes depending on whether an ad is playing or not.
+When an ad is playing, events are prefixed with `ad` and when content is resuming after an ad break, events are prefixed with `content`.
+A `pause` event during an ad would become an `adpause` event, for instance.
+This means from the perspective of a (non-ad) plugin author, video.js will behave just the same whether ads are playing or not.
+And if someoene wants to write a plugin that is ad-aware, those original events are still available for them to hook into.
+
+## Migration
+If you've written your own ad plugin on top of videojs-contrib-ads, there's a couple things you should do to prepare for the upgrade:
+
+- Apply the appropriate prefix to your event handlers.
+If you were listening for `timeupdate` events during ad playback, you should now be listening for `adtimeupdate`.
+Video events that occur during content playback are unaffected.
+- Listen for `contentended` to trigger postrolls instead of `ended`.
+When the content is playing, the `ended` event gets captured and redispatched as `contentended` so that other plugins don't see multiple `ended` events for the same video.
+After the content and postrolls have finished, contrib-ads will fire an `ended` event.
+- Advise your users to include and initialize your plugin before they fire up other plugins.
+contrib-ads will take care of redispatching events but it can't hide them for plugins that are registered earlier in the listener chain.
+
+The extended support for postrolls added a new `postrollTimeout` option, similar to prerolls.
+If you do not wish to play a postroll for a video, you can fire `adtimeout` to proceed to the next video immediately.

node_modules/videojs-contrib-ads/docs/integrator/migration-guides/migrating-to-3.0.md

@@ -0,0 +1,17 @@
+# Migrating to videojs-contrib-ads 3.0.0
+
+One of the best features of video.js is the community of plugins and customizations that has built up around it.
+
+Version 3 of the videojs-contrib-ads plugin is primarily about compatibility with video.js 5 (and, therefore, non-compatibility with video.js 4). Refer to the "[5.0 Change Details](https://github.com/videojs/video.js/wiki/5.0-Change-Details)" document for more on that change.
+
+## Migration
+
+For the most part, ad plugin maintainers will only need to follow the video.js 5 migration changes.
+
+However, there are a few minor changes to videojs-contrib-ads, which are unlikely to affect anyone using the plugin:
+
+- The timer used to trigger an `'adtimeout'` event has been moved to a different property. It is no longer `player.ads.timeout`, but `player.ads.adTimeoutTimeout`. This naming change is less vague and more in line with other timers.
+
+- A new timer is exposed for triggering a synthetic `'ended'` event, `player.ads.resumeEndedTimeout`.
+
+- Internally, timers are now tracked universally using `setTimeout` rather than a mix of `setTimeout`, `requestAnimationFrame`, and the non-standard `setImmediate`. This is not only simpler, but it makes testing easier and more reliable/robust.

node_modules/videojs-contrib-ads/docs/integrator/migration-guides/migrating-to-4.0.md

@@ -0,0 +1,18 @@
+# Migrating to videojs-contrib-ads 4.0.0
+
+Version 4 of videojs-contrib-ads is mainly about improving code quality. Functional
+changes are in support of that effort.
+
+## Migration
+
+* A `playing` event is no longer sent before a preroll ad. This is because a `playing`
+event should only be sent when content actually plays. If your ad plugin relies on
+this event being fired at this time, consider another solution.
+* Contrib-ads expects your plugin to send a "playing" event when an ad starts playing,
+which will be redispatched as "adplaying". This may happen automatically, for example,
+if you play your ad in the content's `video` element.
+* The `contentplayback` event has been removed. Use `playing` instead.
+* `videojs.ads.global.js` and `videojs.ads.global.min.js` have been removed. Use
+`videojs.ads.js` or `videojs.ads.min.js` instead.
+* `videojs.ads.css` is now available in the `dist` folder rather than the `src` folder.
+Your ad plugin should be updated to include it from there.

node_modules/videojs-contrib-ads/docs/integrator/migration-guides/migrating-to-5.0.md

@@ -0,0 +1,13 @@
+# Migrating to videojs-contrib-ads 5.0.0
+
+Version 5 of videojs-contrib-ads includes a rewrite of the Redispatch feature. The goal of
+this rewrite was to provide reliable, maintainable, well-documented, and well-tested
+functionality.
+
+## Migration
+
+* [The behavior of Redispatch is now documented](https://github.com/videojs/videojs-contrib-ads#redispatch). You should review this documentation and confirm that your ad plugin does not have expectations that conflict with the documented behavior.
+* When there is no preroll, you may no longer see extra play events. If your ad plugin relies on play events at the start of a video, you should verify its behavior.
+* The definition of [ad mode](https://github.com/videojs/videojs-contrib-ads#ad-mode-definition) is now documented and consistent. As a result, you may find events that were unprefixed* during ad mode in previous versions that are now prefixed. Any code that listens to unprefixed events during ad mode should be checked.
+
+*An unprefixed event is a normal [media event](https://developer.mozilla.org/en-US/docs/Web/Guide/Events/Media_events) while a prefixed event is one that has been redispatched. For example, `play` is unprefixed and `adplay` is prefixed.

node_modules/videojs-contrib-ads/docs/integrator/migration-guides/migrating-to-6.0.md

@@ -0,0 +1,54 @@
+# Migrating to videojs-contrib-ads 6.0.0
+
+Version 6 of videojs-contrib-ads includes a major refactor and cleanup of the state management logic.
+
+## Migration
+
+* Timeouts have a more intuitive behavior. See the "Timeout behavior changes" section below for more information.
+* Ended events are no longer delayed by 1 second.
+* Ended events due to an ad ending will no longer be allowed to replace the ended event
+that is triggered by linear ad mode ending. Ad plugins must not emit ended events
+after the end of linear ad mode.
+* There will no longer be a `contentended` event when content ends after the first time content ends.
+* `ads.state` has been removed. Methods have been added to replace state checks, such as `ads.isInAdMode()`. See the documentation for a [list of available methods](http://videojs.github.io/videojs-contrib-ads/integrator/api.html). `ads._state` has been
+added, but it is not compatible with the old `ads.state` and should not be inspected by ad plugins.
+* The event parameter `triggerevent` has been removed. It is unlikely that ad plugins used it, but any usage must be migrated.
+* We no longer trigger a `readyforpreroll` event after receiving a `nopreroll` event.
+* adTimeoutTimeout has been removed. It was not part of the documented interface, but make note if your ad plugin inspected it.
+* There is no longer a snapshot object while checking for postrolls. Now a snapshot is only taken when a postroll ad break actually begins.
+* The `contentplayback` event (removed in [4.0.0](https://github.com/videojs/videojs-contrib-ads/blob/cc664517aa0d07398decc0aa5d41974330efc4e4/CHANGELOG.md#400), re-added as deprecated in [4.1.1](https://github.com/videojs/videojs-contrib-ads/blob/cc664517aa0d07398decc0aa5d41974330efc4e4/CHANGELOG.md#411)), has been removed. Use the `playing` event instead.
+* The `adplaying` behavior is an implementation detail and has changed in this update. The `adplaying` event is no longer guaranteed to happen once per ad break. It is not intended to be used to detect the beginning of an ad break. The `ads-pod-started` event should be used instead. The `ads-ad-started` event can be used to detect the start of an individual ad in an ad break. There will be multiple `ads-ad-started` events corresponding to each ad in the ad break.
+
+## Deprecation
+
+Deprecated interfaces will be removed in a future major version update.
+
+* `contentupdate` is now deprecated. It has been replaced by `contentchanged`. `contentupdate` was never intended to fire for the initial source, but over time its behavior eroded. To make migration easier for anyone who depends on the current behavior, we're providing a deprecation period and a new event with correct behavior.
+* `adscanceled` is now deprecated. Instead, use `nopreroll` and `nopostroll`. `adscanceled` was initially intended to function similarly to calling both `nopreroll` and `nopostroll` but it was never fully implemented.
+* `adserror` is now deprecated. Currently this event will skip prerolls when seen before a preroll ad break, skip postrolls if called after contentended and before a postroll ad break, and end linear ad mode if seen during an ad break. It is more declarative for the ad plugin to do these things explicitly with `skipLinearAdMode` and `endLinearAdMode`. In the future, this event will not have any special behavior in contrib-ads. Ad plugins may continue to use it for other purposes.
+
+## Timeout behavior changes
+
+Previous behavior:
+
+* The `timeout` setting was the number of milliseconds that we waited for `adsready` after the `play` event if `adsready` was not before `play`.
+* The `prerollTimeout` setting was the number of milliseconds we waited for `startLinearAdMode` after `readyforpreroll`. It was a separate timeout period after `timeout`.
+* The `postrollTimeout` setting was the number of milliseconds we waited for `startLinearAdMode` after `contentended`.
+
+Previous Defaults:
+
+* timeout: 5000
+* prerollTimeout: 100
+* postrollTimeout: 100
+
+New Behavior:
+
+* The `timeout` setting is now the default setting for all timeouts. It can be overridden by `prerollTimeout` and/or `postrollTimeout`.
+* `prerollTimeout` overrides `timeout` for the number of milliseconds we wait for a preroll ad (the time between `play` and `startLinearAdMode`).
+* `postrollTimeout` overrides `timeout` for the number of milliseconds we wait for a postroll ad (the time between `contentended` and `startLinearAdMode`).
+
+New Defaults:
+
+* timeout: 5000
+* prerollTimeout: no default
+* postrollTimeout: no default