File ViewerDocs
File ViewerDocs
Documentation
Operations2 min readv2.3.0 · Stable

Distribution

File Viewer is distributed through npm, GitHub Releases, Docker and the hosted demo/documentation sites.

File Viewer is distributed through npm, GitHub Releases, Docker and the hosted demo/documentation sites.

NeedRecommended channel
Application integrationnpm packages under @file-viewer/*
Complete framework integrationMatching @file-viewer/*-full package plus /file-viewer/ runtime assets
Static/iframe/offline archivesGitHub Releases
Ready-to-run containerflyfishdev/file-viewer on Docker Hub
Source developmentThis GitHub repository

Large release archives and npm tarballs are not committed to Git history. artifacts/ contains only machine-readable release manifests, status, matrix and schemas; each release record links to its downloadable GitHub Release asset.

*-full already includes preset-all; do not install another preset. Vite uses fileViewerRenderers({ copyAssets:true }) to publish same-version Worker, WASM, font, and vendor assets under file-viewer/ at the deployment base. Other build tools run the full package's npx --no-install file-viewer-copy-assets ./public/file-viewer. Direct CDN web-full, or an intact deployment of its complete dist/, needs no copy step.

Public source build

pnpm install --frozen-lockfile
pnpm build
pnpm docs:build

See Development for the complete public quality gate and Docker for the published image.

Maintainer boundary

Versioning, npm publication, official Docker publication, Cloudflare deployment, repository synchronization and release signing are maintainer-only operations in the complete private workspace. This separation keeps public commands accurate and prevents private operational tooling from leaking into the open-source boundary.

On this page