zentrick / iab-vast-parser Goto Github PK

Version 1.1.2 of gulp-istanbul just got published.

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

As gulp-istanbul is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

See 5eed22f#commitcomment-20401909

Currently when an unknown creative type appears (which is not standards-compliant) the parser fails. It would be valuable if the parsing would continue and just report that one of the nodes failed to parse.

In a live environment, it can happen that non-standard documents show up and we'd like to deal with those.

A browser field is included in package.json, but the file it points to - browser.js is not distributed on npm at the moment (v1.0.2).

I don't believe this makes any difference for javascript web applications, but it does make a difference for react-native applications using metro bundler, which does attempt to make use of the browser field to resolve this dependency but fails when browser.js is not found.

PR #60

As suggested here.

Version 1.5.0 of gulp-load-plugins just got published.

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

As gulp-load-plugins is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Do we want to add support for VAST 1.0 or not?
The current codebase fails on parsing the IAB VAST 1.0 demo documents.