Open integration SDK and Web Component for a self-hosted, licensed Flyfish WPS Viewer runtime. It keeps application integration small while the WPS, ET, and DPS parser and layout engine remain in the commercial core.
中文说明 · Product site · Standalone demo · Commercial license
npm install github:flyfish-dev/wps-viewer-integration#v0.2.0The same package tarball is attached to the GitHub v0.2.0 release. Publishing
under the @flyfish-dev npm scope is prepared but is not required for use.
<flyfish-wps-viewer
viewer-url="https://office.example.com/wps-viewer/demo"
src="https://office.example.com/api/files/42/download"
name="quarterly-report.et"
></flyfish-wps-viewer>
<script type="module">
import { registerFlyfishWpsViewer } from '@flyfish-dev/wps-viewer-integration';
registerFlyfishWpsViewer();
</script>The viewer and document URL must use the same Origin. Put your existing auth, permissions, signed download, and audit logic behind a same-origin route. The file is fetched by the browser and is not uploaded to a conversion service by this package.
import { createWpsViewerUrl } from '@flyfish-dev/wps-viewer-integration';
const url = createWpsViewerUrl({
viewerUrl: 'https://office.example.com/wps-viewer/demo',
source: {
url: 'https://office.example.com/api/files/42/download',
name: 'project-plan.wps',
},
});The <flyfish-wps-viewer> element also exposes open(source) and reload()
and emits viewerloadstart and viewerload events. React and Vue examples are
included under examples/.
This MIT-licensed repository contains only the host API, URL contract, Web Component, types, and examples. It does not contain the parser, layout engine, license verifier, signing material, private corpus, or commercial runtime.
The product site lives at https://wps.file-viewer.app and embeds the separately
maintained evaluator from /demo. The public deployment remains limited to
local-file evaluation; production embedding requires the same /demo route on
a self-hosted, licensed runtime.