Git Product home page Git Product logo

vpaid-ad's Introduction

vpaid-ad

VPAID ad class for extending purposes.

Build Status npm version js-standard-style bitHound Score Greenkeeper badge codecov

This is a reference implementation of VPAID ad. Feel free to extend this to suit your needs. It implements the most basic set of VPAID methods.

Installing using npm

npm i --save vpaid-ad

Usage

You can extend it using this way:

const Linear = require('vpaid-ad/src/linear')
class VpaidAd extends Linear {
  initAd (width, height, viewMode, desiredBitrate, creativeData, environmentVars) {
  	// Do something
    super.initAd(
      width,
      height,
      viewMode,
      desiredBitrate,
      creativeData,
      environmentVars
    )
  }
}

window.getVPAIDAd = function () {
  return new VpaidAd()
}

Your player can then call:

vpaid = window.getVPAIDAd()
vpaid.subscribe(...)

clickThru

There's a special clickThru method that you can use:

vpaid.clickThru({
  url: 'https://example.com',
  id: 'my-id',
  playerHandles: true
})

The above function emits the parameters as both an object and as an array.

As an array:

["https://example.com", "my-id", true]

As an object:

{
  "url": "https://example.com",
  "id": "my-id",
  "playerHandles": true
}

Resources

vpaid-ad's People

Contributors

dependabot-preview[bot] avatar greenkeeper[bot] avatar greenkeeperio-bot avatar kahwee avatar kylevv avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar

vpaid-ad's Issues

An in-range update of babel7 is breaking the build 🚨

There have been updates to the babel7 monorepo:

    • The devDependency @babel/cli was updated from 7.8.3 to 7.8.4.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the babel7 group definition.

babel7 is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

  • Added the new Node.js version to your .travis.yml

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

  • engines was only updated if it defined a single version, not a range.
  • .nvmrc was updated to Node.js 10
  • .travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖


FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of webpack-cli is breaking the build 🚨

The devDependency webpack-cli was updated from 3.3.4 to 3.3.5.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

webpack-cli is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Release Notes for Webpack CLI v3.3.5

Webpack-CLI v3.3.5 has a patch to remove the donation banner that causes some irritation around donations to webpack and for windows users. We've removed this and a full changelog is found here

Commits

The new version differs by 16 commits.

  • 30b1b8d chore: v3.3.5
  • 76b75ac chore: remove donation section
  • 8913928 chore: update pkg lock
  • a37477d cli: remove donation prompt
  • 002a6ac Merge pull request #970 from dhruvdutt/postinstall
  • cd54ba5 chore(scripts): clean opencollective
  • 0c1f6b6 chore(scripts): clean postinstall
  • 313e83e chore(deps): update major versions (#969)
  • 6105ef1 fix(deps): move prettier from dependencies to devDependencies (#968)
  • dad54f4 chore(ts): enables source map in the ts (#961)
  • d7cdab9 Merge pull request #960 from DanielRuf/fix/use-strict
  • 6015bad chore: added await in order to resolve the pending promise (#948)
  • 670efc7 fix: change "usr strict" to "use strict"
  • dc25beb Merge pull request #959 from webpack/fix/deps
  • 69f364e fix: update deps

There are 16 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

can not mute ad after unmute in linear

After unmute, using setAdVolume = 1;, previousAttributes['volume'] remains 0, so

if (this.previousAttributes.volume === volume) {
https://github.com/kahwee/vpaid-ad/blob/master/src/linear.js#L388

became always true, I think the bug somewhere in the set() method

https://github.com/kahwee/vpaid-ad/blob/master/src/linear.js#L48

probably you have to use "current" as "previous" (exchange two strings in set()) or change condition, to make it check current volume attribute:

if (this.getAdVolume() === volume) {

An in-range update of karma is breaking the build 🚨

The devDependency karma was updated from 3.1.0 to 3.1.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

karma is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for v3.1.1

Bug Fixes

  • config: move puppeteer from dependency to dev-dependency (#3193) (f0d52ad), closes #3191
Commits

The new version differs by 2 commits.

  • 361aa3f chore: release v3.1.1
  • f0d52ad fix(config): move puppeteer from dependency to dev-dependency (#3193)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of babel7 is breaking the build 🚨

There have been updates to the babel7 monorepo:

    • The devDependency @babel/cli was updated from 7.1.2 to 7.1.5.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the babel7 group definition.

babel7 is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of babel7 is breaking the build 🚨

There have been updates to the babel7 monorepo:

    • The devDependency @babel/cli was updated from 7.1.2 to 7.1.5.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the babel7 group definition.

babel7 is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

An in-range update of webpack is breaking the build 🚨

The devDependency webpack was updated from 4.20.2 to 4.21.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

webpack is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for v4.21.0

Features

  • add output.libraryTarget: "amd-require" which generates a AMD require([], ...) wrapper instead of a define([], ...) wrapper
  • support arrays of strings passed to output.library, which exposes the library to a subproperty

Bugfixes

  • fix cases where __webpack_require__.e is used at runtime but is not defined in the bundle
  • fix behavior of externals of global type

Performance

  • Some performance improvements to the chunk graph generation
Commits

The new version differs by 37 commits.

  • 432d2a3 4.21.0
  • 0fb6c60 Merge pull request #7038 from marcusdarmstrong/marcusdarmstrong-external-module-fix
  • 15b6f8b make afterEach async
  • 7bc5c98 Merge branch 'master' into marcusdarmstrong-external-module-fix
  • 2228daf Merge pull request #8230 from webpack/revert-8120-rh-silent-reporter
  • fadf875 remove dependency
  • 7c0b209 Revert "Re-enable jest-silent-reporter #hacktoberfest"
  • a868789 Merge pull request #8143 from MLoughry/miclo/optimize-chunk-graph-generation
  • 1d71ede Make changes suggested by @sokra to optimize chunk graph generation
  • 4d3fe00 Merge pull request #8134 from fscherwi/update-coveralls
  • 86f56bf update coveralls
  • 4c461e2 Merge pull request #8120 from rickhanlonii/rh-silent-reporter
  • 9fe42e7 Merge pull request #8118 from webpack/bugfix/issue-8110
  • 0b6ad2a Don't be clever with the set command because idk windows
  • 148016e Rerun yarn

There are 37 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.