You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Releases are staged on npm instead of published directly: the release workflow runs npm stage publish
(Trusted Publishing, provenance), and a version becomes public only when a maintainer approves it on
npmjs.com with two-factor authentication; the workflow pins npm 11.20.0 for it (staged publishing needs 11.15.0+).
The README opens with the Quantum Media Technologies wordmark and closes with a "Made by" line, both linking to www.qmediat.io/open-source; package.jsonhomepage points there (author already carried the company line).
Development: the project builds with TypeScript 7 (the native compiler). The published JavaScript is byte-identical
to 1.0.3; the type declarations describe the same types (only the order of union members and properties and the
quote style differ) and the source maps are regenerated. The TypeScript 7 npm package ships only tsc — no tsserver and no JavaScript API — so an editor set to use the workspace TypeScript version cannot load it from node_modules; use the editor's bundled one.
The release workflow checks that CHANGELOG.md has a section for the version, asks npm once whether the version
is already public and stops on any answer other than yes or no (a registry error used to read as "not public"),
runs an npm pinned by version and by the sha512 of its tarball, and names a failed stage in the run summary.