Adrien Joly

Hi! Indeed, the testing instructions are incorrect. `ava` is a development dependency of `pdfreader`, so it's not installed when you add `pdfreader` as a dependency of your own project. Can...

Even if you run `npx ava` from the `pdfreader` directory?

> Just realised there is no "test" folder inside "node_modules/pdfreader", because its listed in ".npmignore" [to reduce package size](https://github.com/adrienjoly/npm-pdfreader/commit/03d6155d1895080b8a525c7564c9f7e088b2b24c). Good catch! That makes sense, as test files are not needed...

It looks like the software that produced that PDF has a particular way to split words into text entries... Maybe because the paragraph of text was justified, i.e. adding variable...

... or https://github.com/adrienjoly/eval

@posix4e I don't think anyone is, unfortunately... As @atotic said, I guess that the component could catch the error. But then, how should it react? Do you think of any...

Maybe @sbeleidy (creator of [login-fire](https://www.webcomponents.org/element/convoo/login-fire)) has an idea?

Solved this problem by adding a `properties: {}` property after my `allOf` property, in the definition that was causing this error. => ```js // [...] definitions: { // [...] PutConfigResponse:...

Reproduced bug on /test/sample.html: 1. Open [/test/sample.html](https://cdn.rawgit.com/adrienjoly/playemjs/master/test/sample.html) 2. Make sure that two videos are played sequentially: the one with a beeping counter + the one with a dinosaur / godzilla...

Calling `playVideo()` programmatically instead of relying on Youtube's `autoplay` parameter does not fix this issue, unfortunately... (cf https://github.com/adrienjoly/playemjs/pull/16)