Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TypeError: this.storage_.values is not a function or its return value is not iterable #8845

Open
kikklop opened this issue Aug 27, 2024 · 2 comments
Labels
needs: triage This issue needs to be reviewed

Comments

@kikklop
Copy link

kikklop commented Aug 27, 2024

Description

After updating videojs on 8.17.3 appears this type error which I cant resolve because seems its from depended on videojs/http-streaming. Videojs has his version of http-streaming in dependecies so I cant to change this version.
Have you already dealt with a similar error?

Appreciate any help thanks!

videojs_typeerror

Reduced test case

none

Steps to reproduce

  1. Update 8.17.3
  2. Try run HLS player

Errors

Uncaught TypeError: this.storage_.values is not a function or its return value is not iterable

What version of Video.js are you using?

8.17.3

Video.js plugins used.

"videojs-contrib-ads": "^7.5.2", "videojs-contrib-eme": "^5.5.0", "videojs-hotkeys": "^0.2.28", "videojs-ima": "2.3.0", "videojs-markers-plugin": "^1.0.2", "videojs-mux": "4.17.0",

What browser(s) including version(s) does this occur with?

Chrome 128.0.6613.84

What OS(es) and version(s) does this occur with?

Mac

@kikklop kikklop added the needs: triage This issue needs to be reviewed label Aug 27, 2024
Copy link

welcome bot commented Aug 27, 2024

👋 Thanks for opening your first issue here! 👋

If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can.
To help make it easier for us to investigate your issue, please follow the contributing guidelines.

@gkatsev
Copy link
Member

gkatsev commented Aug 27, 2024

that's unexpected. The map object is always set and should always be available. Trying out on https://videojs-http-streaming.netlify.app/, and the call to values() returns an iterable as expected.
Are you able to reproduce it on your end on a reduced test case? It seems like you have some wrapper around video.js. Is it possible that it changes the code somehow or does it add somehow override the global Map object?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs: triage This issue needs to be reviewed
Projects
None yet
Development

No branches or pull requests

2 participants