This repository was archived by the owner on Oct 7, 2026. It is now read-only.
Repository navigation
chore: end of life, point to Video.js 10 - #387
Merged
Merged
Conversation
Add SECURITY.md and AGENTS.md, replace the 'deprecated soon' banner in the README and on vimejs.com, and add end-of-life notices to the package READMEs, CONTRIBUTING.md, and the docs introduction and installation pages. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Lead the package descriptions with the deprecation, ship an AGENTS.md in every package, tag vm-player @deprecated, and log a one-time console notice when the first player connects. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Prettier 2 joins a bare '> [!IMPORTANT]' line into the next one, which stops GitHub rendering the alert, so each alert marker is followed by an empty quote line. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Vercel deploys have failed since late 2024 with ERR_OSSL_EVP_UNSUPPORTED: Docusaurus 2 beta's webpack hashes with md4, which OpenSSL 3 dropped. Map md4 to sha256 in the config so the site builds on current Node without NODE_OPTIONS, which Node 16 rejects. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
packages/angular/package.json gained publishConfig.directory without a lockfile update, so CI installs (Vercel's included) failed with ERR_PNPM_OUTDATED_LOCKFILE. Regenerated with pnpm 7 --lockfile-only; the only resolution change is the hls.js dev dependency ("latest") moving to 1.7.3, and all packages still build.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Vercel fails these deploys before building, which matches a discontinued Node.js version in the project settings. engines.node overrides that setting; the install, core build, and docs build all pass on Node 22. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
engines.node didn't change the result: Vercel still fails these deploys within a second of creating them, before any build step, so the cause is in the project or team settings. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This branch had an error being deployed
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Vime is end of life: no further fixes, including security fixes. After this merges, 5.4.2 ships the notices to npm, every
@vime/*version is deprecated, the backlog is closed, and the repository is archived. This mirrors vidstack/player#1867, without the triage workflow since the repo gets archived.Docs and repository
SECURITY.md: no supported versions, and a pointer to Video.js 10.AGENTS.mdat the root and in every package. They send agents to the Video.js skill, the installation guide's AI Quickstart prompt, and the Vidstack migration guide for the closest concept mapping, since there's no Vime-specific guide. Each package'sAGENTS.mdis added tofiles(or to ng-packagrassetsfor Angular), so it ships on npm.CONTRIBUTING.md, and the docs introduction and installation pages (a:::cautioncallout).Package deprecation
video.jsandvideojsare added to the keywords.vm-playeris tagged@deprecated, which carries into the published types.console.infowhen the first player connects, skipped during server rendering (Build.isBrowser).Checks
pnpm@6.22.0pin is stale; pnpm 6 can't runpnpm -F).npm pack --dry-runshowsAGENTS.mdandREADME.mdin all six tarballs, including Angular'sdist.vm-playerentry, and@deprecatedis indist/types.> [!IMPORTANT]line into the next line, which breaks GitHub alerts, so each alert marker is followed by an empty>line. GitHub's Markdown API confirms they render as alerts.vimejs.com
Production deploys have failed since November 2024, so vimejs.com still serves the October 2023 build. This PR fixes the two failures I could reproduce:
ERR_PNPM_OUTDATED_LOCKFILE:packages/angular/package.jsongainedpublishConfig.directorywithout a lockfile update. I regenerated the lockfile with pnpm 7 (--lockfile-only). The only resolution change is thehls.jsdev dependency ("latest"), which moves to 1.7.3; every package still builds.ERR_OSSL_EVP_UNSUPPORTED, because Docusaurus 2 beta's webpack hashes with md4, which OpenSSL 3 dropped.docusaurus.config.jsnow maps md4 to sha256. I used that instead ofNODE_OPTIONS=--openssl-legacy-provider, which Node 16 rejects.From a fresh clone on Node 22, a frozen install,
npm run build:api, and the docs build all pass, and the new callout is in the output. Vercel still fails each preview within a second of creating it, before any build step runs, so something in thevidstackteam's project settings is blocking it. I can't see those settings with my access.🤖 Generated with Claude Code