HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
videojs
v10
Creative & Media2026–2026
videojs / v10 · Archived

v10

🚚 Video.js v10 has moved to videojs/video.js

4Distinct people
9Mentions
0Explicit recommenders
1KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

🚚 Video.js v10 has moved to videojs/video.js

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 5:58:53 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by hour9 dated mentions

Observed mentions: 2026-03-25 01:38:12 UTC to 2026-03-25 22:12:27 UTC.

0122026-03-25 01:00:00 UTC to 2026-03-25 02:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 commentsMar 25, 01:002026-03-25 02:00:00 UTC to 2026-03-25 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-25 03:00:00 UTC to 2026-03-25 04:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-25 04:00:00 UTC to 2026-03-25 05:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-25 05:00:00 UTC to 2026-03-25 06:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-03-25 06:00:00 UTC to 2026-03-25 07:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-03-25 07:00:00 UTC to 2026-03-25 08:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-25 08:00:00 UTC to 2026-03-25 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-25 09:00:00 UTC to 2026-03-25 10:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-25 10:00:00 UTC to 2026-03-25 11:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-25 11:00:00 UTC to 2026-03-25 12:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMar 25, 11:002026-03-25 12:00:00 UTC to 2026-03-25 13:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-25 13:00:00 UTC to 2026-03-25 14:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2026-03-25 14:00:00 UTC to 2026-03-25 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-25 15:00:00 UTC to 2026-03-25 16:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-25 16:00:00 UTC to 2026-03-25 17:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-25 17:00:00 UTC to 2026-03-25 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-25 18:00:00 UTC to 2026-03-25 19:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-25 19:00:00 UTC to 2026-03-25 20:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-25 20:00:00 UTC to 2026-03-25 21:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-03-25 21:00:00 UTC to 2026-03-25 22:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-25 22:00:00 UTC to 2026-03-25 23:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMar 25, 22:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Mar 25, 01:002026-03-25 01:00:00 UTC2026-03-25 02:00:00 UTC202
Mar 25, 02:002026-03-25 02:00:00 UTC2026-03-25 03:00:00 UTC000
Mar 25, 03:002026-03-25 03:00:00 UTC2026-03-25 04:00:00 UTC000
Mar 25, 04:002026-03-25 04:00:00 UTC2026-03-25 05:00:00 UTC000
Mar 25, 05:002026-03-25 05:00:00 UTC2026-03-25 06:00:00 UTC101
Mar 25, 06:002026-03-25 06:00:00 UTC2026-03-25 07:00:00 UTC101
Mar 25, 07:002026-03-25 07:00:00 UTC2026-03-25 08:00:00 UTC000
Mar 25, 08:002026-03-25 08:00:00 UTC2026-03-25 09:00:00 UTC000
Mar 25, 09:002026-03-25 09:00:00 UTC2026-03-25 10:00:00 UTC000
Mar 25, 10:002026-03-25 10:00:00 UTC2026-03-25 11:00:00 UTC000
Mar 25, 11:002026-03-25 11:00:00 UTC2026-03-25 12:00:00 UTC101
Mar 25, 12:002026-03-25 12:00:00 UTC2026-03-25 13:00:00 UTC000
Mar 25, 13:002026-03-25 13:00:00 UTC2026-03-25 14:00:00 UTC202
Mar 25, 14:002026-03-25 14:00:00 UTC2026-03-25 15:00:00 UTC000
Mar 25, 15:002026-03-25 15:00:00 UTC2026-03-25 16:00:00 UTC000
Mar 25, 16:002026-03-25 16:00:00 UTC2026-03-25 17:00:00 UTC000
Mar 25, 17:002026-03-25 17:00:00 UTC2026-03-25 18:00:00 UTC000
Mar 25, 18:002026-03-25 18:00:00 UTC2026-03-25 19:00:00 UTC000
Mar 25, 19:002026-03-25 19:00:00 UTC2026-03-25 20:00:00 UTC000
Mar 25, 20:002026-03-25 20:00:00 UTC2026-03-25 21:00:00 UTC101
Mar 25, 21:002026-03-25 21:00:00 UTC2026-03-25 22:00:00 UTC000
Mar 25, 22:002026-03-25 22:00:00 UTC2026-03-25 23:00:00 UTC101

What Hacker News says

1 sources
Hey there, I'm on the Video.js team! Sounds like your context provider approach is already in the right ballpark! Some background: our store[1] which was inspired by Zustand[2] is created and passed down via context too. This is the central state management piece of our library and where we imagine most devs will build on for extending and customizing to their needs. Updates are handled via simple store actions like `store.play()`, `store.setVolume(10)`, etc. Those actions are generally called in response to DOM events. On the events side of things, rather than registering event listeners directly, in v10 you'd subscribe to the store instead. Something like `store.subscribe(callback)`, or in React you'd use our `usePlayer`[3] hook. The store is the single source of truth, so rather than listening to the underlying media element directly,
Read the rest
you're observing state changes. --- So far with v10 we haven't been thinking about "plugins" in the traditional sense either. If I had to guess at what it would look like, it'd be three things: 1. Custom store slices[4] so plugins can extend the store with their own state and actions 2. A middleware layer that plugs into the store's action pipeline so a plugin could intercept or react to actions before or after they're applied, similiar to Zustand middleware, or even in some ways like Video.js v8 middleware[5] 3. UI components that plugins can ship which use our core primitives for accessing the store, subscribing to state, etc. I believe that'd cover the vast majority of what plugins needed in v8. We haven't nailed down the exact API yet but that's the direction we're leaning towards. We're still actively working on both the library and our docs so I don't have somewhere I can link to for these just yet (sadly)! We're likely targeting sooner, but GA (end of June) is the deadline. I should also add... one thing we prototyped early on that may return: tracking end-to-end requests through the store. A DOM event triggers a store action like play, which calls `video.play()`, which then waits for the media event response (play, error, etc.). It worked really well and lines up nicely with the middleware direction. [1]: https://github.com/videojs/v10/tree/main/packages/store [2]: https://github.com/pmndrs/zustand [3]: https://videojs.org/docs/framework/react/reference/use-playe... [4]: https://zustand.docs.pmnd.rs/learn/guides/slices-pattern#sli... [5]: https://legacy.videojs.org/guides/middleware/
In Show HN: I took back Video.js after 16 years and we rewrote it to be 88% smaller

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.