Add set source

[yoriiis]

Initial PR #153

cc/ @rtritto

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Updated (UTC)
vlite	Ready	Preview	Nov 19, 2025 0:31am

[yoriiis]

Add parameter value info

[yoriiis]

Add note about to play trigger by this method

[rtritto]

@yoriiis Thanks, what about to call the setSource method like src (equal to video.js, short and preferred to have less migrations impacts)?

[yoriiis]

@yoriiis Thanks, what about to call the setSource method like src (equal to video.js, short and preferred to have less migrations impacts)?

It's a new method, so I don't really see how it limits migration.

In my opinion, src does not refer to a method. I prefer to keep the nomenclature used for other methods (getter/setter), which I find clearer.

[yoriiis]

@rtritto Could you test this feature? Since you were the one who requested it.
It is available on all providers

[rtritto]

It's a new method, so I don't really see how it limits migration.

Having different method names the migration from video.js to vLite is:

- videoRef.src(newSrc)
+ videoRef.setSource(newSrc)

It's not a limit, but if both methods have same name, you have 1 less reference to migrate.

Another advantage is that src is shorter, so less characters are used (less code size).

---

In my opinion, src does not refer to a method. I prefer to keep the nomenclature used for other methods (getter/setter), which I find clearer.

What do you think about, in another PR, the logic of all methods of the getter/setter can be improved.
E.g. for source:

• getter: playerRef.src
• setter: playerRef.src(newSrc)

---

@rtritto Could you test this feature?

Yes

[rtritto]

@yoriiis I can't test, I got cross-origin ~ header CORS “Access-Control-Allow-Origin” ~ 301 on "https://yoriiis.github.io/cdn/static/vlitejs/demo-video-html5.mp4".

[yoriiis]

@rtritto I'm happy you planned to migrate from Video.js to vLitejs!

I understand your point about migration, but I prefer to stick to my own terminology, which I find clearer. And, the goal of this library is not to be identical to video.js

[yoriiis]

@yoriiis I can't test, I got cross-origin ~ header CORS “Access-Control-Allow-Origin” ~ 301 on "https://yoriiis.github.io/cdn/static/vlitejs/demo-video-html5.mp4".

You can access the Vercel preview URL?

The error appears when you submit a new source?

If you have the project in local perhaps? I will check the error soon