npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@videojs/core

v10.0.0-beta.26

Published

Core components and utilities for Video.js

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

squarebracketsquarebracketvideojs-uservideojs-usertjaneczkotjaneczkogkatsevgkatsevheffheffmmccluremmcclurebrandonocaseybrandonocaseyforbesjoforbesjogesingergesingerimbcmdthimbcmdthincomplincomplmjneilmjneilokaramianokaramianldayldayesskesskmmccmmccabarstowabarstowddashkevichddashkevichbrightcove-userbrightcove-userluwesluwesdecepulisdecepulissam_pottssam_potts

Keywords

coreplayervideojs

Readme

@videojs/core

package-badge

⚠️ Beta Close to stable. Experimental adoption in real projects.

Overview

@videojs/core provides runtime-agnostic core components and utilities shared across Video.js packages. These are foundational building blocks used by platform-specific implementations (DOM, HTML, React, React Native) to create consistent media player experiences.

Update i18n copy

The i18n source of truth lives in src/core/i18n/locales. Translation keys are opaque semantic paths such as buttons.play; English copy is stored separately, so it can change without renaming the key.

When you add, rename, or remove player copy:

  1. Update src/core/i18n/locales/en.ts. Add the English value under a short semantic path. Keep required {placeholder} tokens in the value.
  2. Update every non-English file in src/core/i18n/locales. Use the same nested path, move an existing translation when the meaning is unchanged, and add or remove values with the English source.
  3. Run pnpm -F @videojs/core run generate:locales. This validates locale completeness and refreshes text descriptors, locale loaders, CDN registration modules, and HTML/React re-exports.
  4. Run pnpm -F @videojs/core run generate:i18n-types. This refreshes TranslationParams from the English keys and placeholders.
  5. Update call sites and tests. Import the generated text descriptor from src/core/i18n/text/<group>.ts; do not duplicate the key and English fallback at each call site.
  6. Run focused tests and typecheck. At minimum, run the package tests that cover the changed copy and pnpm typecheck.

Community

If you need help with anything related to Video.js v10, or if you'd like to casually chat with other members:

License

Apache-2.0