Skip to content
This repository was archived by the owner on Oct 7, 2026. It is now read-only.

chore: end of life, point to Video.js 10 - #387

Merged
mihar-22 merged 7 commits into
mainfrom
chore/end-of-life
Oct 6, 2026
Merged

mihar-22 merged 7 commits into
mainfrom
chore/end-of-life

Conversation

@mihar-22

@mihar-22 mihar-22 commented Oct 6, 2026 •

Copy link
Copy Markdown
Contributor

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.md at 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's AGENTS.md is added to files (or to ng-packagr assets for Angular), so it ships on npm.
  • The "Vime will be deprecated soon!" banner in the README and on vimejs.com now says Vime is no longer maintained and links to Video.js 10.
  • End-of-life notices in every package README, CONTRIBUTING.md, and the docs introduction and installation pages (a :::caution callout).

Package deprecation

  • Package descriptions lead with the deprecation, and video.js and videojs are added to the keywords.
  • vm-player is tagged @deprecated, which carries into the published types.
  • A one-time console.info when the first player connects, skipped during server rendering (Build.isBrowser).

Checks

  • All six packages build on Node 16 with pnpm 7 (the lockfile is v5.4, so the pnpm@6.22.0 pin is stale; pnpm 6 can't run pnpm -F).
  • npm pack --dry-run shows AGENTS.md and README.md in all six tarballs, including Angular's dist.
  • The console notice is in the built vm-player entry, and @deprecated is in dist/types.
  • Prettier passes on every changed file. Prettier 2 merges a bare > [!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:

  • Frozen installs failed with ERR_PNPM_OUTDATED_LOCKFILE: packages/angular/package.json gained publishConfig.directory without a lockfile update. I regenerated the lockfile with pnpm 7 (--lockfile-only). The only resolution change is the hls.js dev dependency ("latest"), which moves to 1.7.3; every package still builds.
  • The docs build failed on Node 17+ with ERR_OSSL_EVP_UNSUPPORTED, because Docusaurus 2 beta's webpack hashes with md4, which OpenSSL 3 dropped. docusaurus.config.js now maps md4 to sha256. I used that instead of NODE_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 the vidstack team's project settings is blocking it. I can't see those settings with my access.

🤖 Generated with Claude Code

mihar-22 and others added 3 commits October 5, 2026 20:44
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>
@vercel

vercel Bot commented Oct 6, 2026 •

Copy link
Copy Markdown

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

Project Deployment Actions Updated
vime Error Error Oct 6, 2026 3:53am UTC

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

1 failed deployment
Preview — 13f75be8 Deployed Oct 6, 2026 by vercel[bot]
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant