Repository navigation
Conversation
The `video.js` package no longer ships a player. It drops the `@videojs/html` dependency, the element registration, and the re-export, so the root carries only the Video.js 8 stubs, the `video.js/errors` registry, and the empty v8 stylesheet. The README routes readers to `@videojs/html`, `@videojs/react`, or `@videojs/cdn`, adds an AI quickstart through `@videojs/cli agents`, and says Video.js 8 stays maintained by Brightcove. A published AGENTS.md gives coding agents the same routing.
Every `@videojs/html` and `@videojs/react` install now carries `video.js@10`, so its routing README, published AGENTS.md, and coded v8 errors sit in the project's dependencies. Nothing imports it, so bundles are unchanged. The README and AGENTS.md explain why `video.js` appears in a v10 install, and the maintainer rules forbid importing it from `@videojs/*` or giving it dependencies of its own.
The registry suite only packed `@videojs/*` workspace packages, so the consumer apps resolved `@videojs/core`'s new `video.js` dependency from npm, which has no 10.x release. Pack every named workspace package instead.
The published guide now addresses only agents working in a project that installed video.js.
Link the canonical /docs/guides/installation/<route> pages, which includes the CDN guide that 404ed, add the Vue and Svelte guides, and show the jsDelivr script plus player markup for script-tag installs.
Video.js 10 does export createPlayer factories, so the init summary now names what was removed: setting up a player from an element or id. Importing the stubs does not throw; calling them does.
…uter-readme # Conflicts: # packages/video.js/README.md
Drop `private`, so the release job's recursive publish ships `video.js` with the rest of the linked version group, under `latest` for stable releases. pnpm publishes it before `@videojs/core`, which pins its exact version. Add the homepage, publish PR previews of `video.js` so preview `@videojs/core` installs resolve, and tag its undocumented exports `@internal` now that the API stability check covers it.
The migration guide and both llms.txt headers said the `video.js` npm package is still Video.js 8. The site deploys in the same release job that publishes `video.js@10`, so they now say it contains no player and to install `video.js@8` to stay on Video.js 8.
The stubs are the public Video.js 8 surface, so editors now strike through `videojs()` and its static methods and link the error page for each code. The `video.js/errors` helpers stay `@internal`.
The workspace contract test rejects an AI Quickstart in any public package outside the installation-backed set. Publishing `video.js` made it public, and its README routes installs to the framework packages with the same AI Quickstart, so the test now expects it there. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
`videojs/video.js` now hosts Video.js 10, and Video.js 8 lives in `videojs/videojs-v8`. The README and AGENTS.md sent v8 users to `videojs/video.js` and the README linked discussions in `videojs/v10`. They also promised v8 bug fixes, but SECURITY.md limits v8 to security fixes until October 1, 2028, so they say that now. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…atest # Conflicts: # packages/video.js/package.json
The migration guide's stay-on-v8 sentence linked `videojs/video.js`, which now hosts Video.js 10. Video.js 8 lives in `videojs/videojs-v8`. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
4 tasks
✅ Deploy Preview for vjs-registry ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for vjs10-site ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
@videojs/cdn
@videojs/cli
@videojs/core
@videojs/element
@videojs/html
@videojs/media
@videojs/react
@videojs/spf
@videojs/store
@videojs/utils
video.js
@videojs/cloudflare-video
@videojs/dash-video
@videojs/hlsjs-video
@videojs/mux-audio
@videojs/mux-video
@videojs/native-hls-video
@videojs/playerjs-video
@videojs/shaka-video
@videojs/spotify-audio
@videojs/tiktok-video
@videojs/twitch-video
@videojs/vimeo-video
@videojs/wistia-video
@videojs/youtube-video
@videojs/google-cast
@videojs/mux-data
commit: |
Contributor
📦 Bundle Size Report🎨 @videojs/html — no changesPresets (7)
Media (19)
Players (5)
Skins (53)
UI Components (62)
⚛️ @videojs/react — no changesPresets (7)
Media (23)
Extensions (2)
Players (5)
Skins (34)
UI Components (39)
🧩 @videojs/core — no changesEntries (76)
🏷️ @videojs/element — no changesEntries (2)
📦 @videojs/store — no changesEntries (3)
🔧 @videojs/utils — no changesEntries (13)
📦 @videojs/cdn — no changes📦 @videojs/cloudflare-video — no changes📦 @videojs/dash-video — no changes📦 @videojs/google-cast — no changes📦 @videojs/hlsjs-video — no changes📦 @videojs/media — no changesEntries (3)
📦 @videojs/mux — no changes📦 @videojs/mux-audio — no changesEntries (2)
📦 @videojs/mux-data — no changes📦 @videojs/mux-video — no changesEntries (2)
📦 @videojs/native-hls-video — no changes📦 @videojs/playerjs-video — no changes📦 @videojs/shaka-video — no changes📦 @videojs/spf — no changesEntries (7)
📦 @videojs/spotify-audio — no changes📦 @videojs/tiktok-video — no changes📦 @videojs/twitch-video — no changes📦 @videojs/other — 1 small size change
Entries (3)
📦 @videojs/vimeo-video — no changes📦 @videojs/wistia-video — no changesEntries (2)
📦 @videojs/youtube-video — no changesℹ️ How to interpretEach entry is independently bundled, minified, and brotli-compressed. Initial size includes its static import graph; lazy dynamic chunks are reported separately. Entries are not additive because their dependency graphs overlap. Preset rows represent realistic combined bundles. Changes of 300 B or less across initial, lazy, and total size are collapsed, not discarded. Run |
luwes
approved these changes
Oct 7, 2026
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
`video.js` is private, so a release would publish `@videojs/core` depending on a `video.js@10` that npm does not have. Publish `video.js` on its own first; the dependency returns in #9259. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Drop `private` so the release job publishes `video.js` under `latest`, and include it in PR previews. Tag the Video.js 8 stubs `@deprecated` and the `video.js/errors` helpers `@internal` for the API stability check, expect the AI Quickstart in its README, and say on the site that `video.js@10` has no player and `video.js@8` keeps Video.js 8. Carried over from #9259, which now only restores the `@videojs/core` dependency. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1 task
Restore the dependency that #9477 drops so `video.js` could publish on its own. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
`latest` stays on Video.js 8, so `npm install video.js` and unversioned CDN URLs keep resolving v8 until `video.js` is promoted. Publish it before the other packages so a dependent never pins a version npm lacks. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
`video.js@10` publishes under `next`, so the default install is still Video.js 8. Keep the migration guide's link to the Video.js 8 repository at videojs/videojs-v8. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stacked on #9477. Until #9477 merges, this diff also shows its changes. Only
packages/core/package.jsonandpnpm-lock.yamlbelong to this PR.Summary
Restores
@videojs/core's dependency onvideo.js, which #9258 added and #9477 drops sovideo.jscould publish on its own. Merge this oncevideo.js@10is on npm, so core never pins avideo.jsversion npm lacks.Changes
@videojs/coredepends onvideo.jsagain (workspace:*, published as an exact version). npm resolves exact versions whatever the dist-tag, sovideo.jsstaying onnextdoesn't affect core installs.video.jsbefore the other packages (feat(video.js): publish video.js to npm under next #9477), so in a release that ships both, core's dependency is already on npm.Everything else that was here (making
video.jspublic, the stability tags, the contract test, pkg-pr-new, the migration guide link) moved to #9477.video.jsnow publishes undernextinstead oflatest.Testing
pnpm install --frozen-lockfile: the core importer matchesmainbefore feat(video.js): publish video.js to npm under next #9477.🤖 Generated with Claude Code