@nomercy-entertainment/nomercy-video-player 2.2.8 → 2.2.9

package/CHANGELOG.md

@@ -2,6 +2,12 @@
 
 ## [Unreleased]
 
+## [2.2.9] — 2026-10-23
+
+### Fixed
+
+- The buffering and loading toast shows text instead of the raw key `plugin.desktop-ui.message.buffering` in a language that has no desktop-ui locale file (needs core 2.2.9).
+
 ## [2.2.8] — 2026-10-21
 
 ### Fixed

package/CONTRIBUTING.md

@@ -13,16 +13,17 @@ Thanks for your interest in `@nomercy-entertainment/nomercy-video-player`. This
 ```bash
 git clone https://github.com/NoMercy-Entertainment/nomercy-video-player.git
 cd nomercy-video-player
-npm install
-npm test          # vitest run (unit tests must pass)
-npm run typecheck # tsc --noEmit
-npm run build     # writes dist/
+corepack enable   # once; picks yarn 4 from package.json
+yarn install
+yarn test         # vitest run (unit tests must pass)
+yarn typecheck    # tsc --noEmit
+yarn build        # writes dist/
 ```
 
 The package also has a real-browser e2e suite built with Playwright:
 
 ```bash
-npm run test:e2e  # runs pretest:e2e (generates fixtures via the NoMercy ffmpeg fork) then npx playwright test
+yarn test:e2e     # runs pretest:e2e (generates fixtures via the NoMercy ffmpeg fork) then playwright test
 ```
 
 The `pretest:e2e` step downloads and runs the NoMercy ffmpeg fork to produce short test media files. The generated fixtures go into `e2e/media/` and are not committed. Running `test:e2e` for the first time may take a few minutes on a slow connection.
@@ -32,7 +33,7 @@ The `pretest:e2e` step downloads and runs the NoMercy ffmpeg fork to produce sho
 - Branch off `master`. Feature branches: `feat/<short-description>`. Fixes: `fix/<short-description>`.
 - Commit messages follow [Conventional Commits](https://www.conventionalcommits.org/) (`feat`, `fix`, `chore`, `docs`, `refactor`, `test`, `perf`, `ci`). Imperative, lowercase subject, no trailing period.
 - Tests required for new features. Bug fixes should include a regression test.
-- Run `npm run lint:fix` before pushing. CI rejects lint failures.
+- Run `yarn lint:fix` before pushing. CI rejects lint failures.
 - No `Co-Authored-By` trailers unless we paired live.
 
 ## Plugin contributions

package/RELEASING.md

@@ -15,13 +15,13 @@ install with an explicit tag or version during the rc phase.
 ## Build
 
 The package ships two artifacts from one `dist/`: the ESM build from `tsc` and the
-IIFE CDN bundle from Vite (`vite.iife.config.ts`). `npm run build` wipes `dist/` before
+IIFE CDN bundle from Vite (`vite.iife.config.ts`). `yarn build` wipes `dist/` before
 it compiles, so the bundle must always be produced after it, never before.
 
 ```
-npm run build       # tsc ESM dist + translation and asset passes
-npm run build:iife  # Vite IIFE bundle into the same dist/
-npm run build:all   # both, in the right order
+yarn build       # tsc ESM dist + translation and asset passes
+yarn build:iife  # Vite IIFE bundle into the same dist/
+yarn build:all   # both, in the right order
 ```
 
 The `prepublishOnly` hook runs `build:all`, so a publish from any environment packs
@@ -39,5 +39,5 @@ verification) lives in the core repo's RELEASING.md. Steps specific to this pack
    convention, not mechanics.
 4. Add a `[2.0.0]` entry to `CHANGELOG.md` summarizing changes since the last rc.
 5. After core `2.0.0` is on the registry, run
-   `npm update @nomercy-entertainment/nomercy-player-core` before publishing so the
+   `yarn up @nomercy-entertainment/nomercy-player-core` before publishing so the
    build scripts and lockfile come from the stable core.