LensPDFViewer (one-line viewer)

LensPDFViewer

The default composition. Drop it into any React 19 project and you have a working PDF viewer — no host-context wiring, no per-page mounting, no worrying about pdf.js workers.

import { LensPDFViewer } from "@printwithsynergy/lens-pdf";

export function MyViewer() {
  return <LensPDFViewer pdfUrl="https://example.com/file.pdf" />;
}

What it does

• Builds a pdf.js fallback adapter from pdfUrl and configures the worker URL.
• Wraps ViewerHostContext and (optionally) ViewerServicesContext.
• Auto-discovers page count, page dimensions, and OCG layers from the PDF.
• Renders every page in a scrollable, lazy-loaded virtual list (or one at a time with mode="single").
• Seeds initial layer state from the PDF’s defaults (default-on layers enabled, default-off off).
• Ships a responsive default toolbar with zoom, layers, color picker, and measure tool.
• Reflows to a bottom-drawer layout under 768 px wide.

Props

Prop	Type	Default	Notes
pdfUrl	string	required	PDF URL fetched by the user’s browser. Sign / scope upstream — see Security.
workerSrc	string	defaultPdfWorkerSrc (unpkg, pinned to bundled pdfjs-dist version)	Override to self-host the pdf.js worker.
services	ViewerServices	(unset)	Pass when your host has a backend with separations / densitometer / TAC / annotations / reports. Components for unwired services hide silently.
tokens	ThemeTokens	defaultThemeTokens	Brand palette.
className	string	""	Class hook on the outer shell.
mode	"scroll" | "single"	"scroll"	Page rendering mode.
tools	ReadonlyArray<"zoom"|"layers"|"color-picker"|"measure">	all four	Toolbar contents. Pass [] for no toolbar.
initialZoom	number	100	Starting zoom percent.
brand	string	(none)	Optional brand label rendered in the top-left of the toolbar.
header	(state: LensPDFViewerState) => ReactNode	(built-in toolbar)	Replace the default toolbar. Receives viewer state.
sidebar	(state: LensPDFViewerState) => ReactNode	(none)	Inject a sidebar next to the page list.
footer	ReactNode	(none)	Static footer content rendered below the viewer stage.

What gets hidden when no services are wired

The composition relies on the host-agnostic capability-detection contract from fallback.md. With only pdfUrl set:

Component	Visible	Notes
Page rendering, navigation, zoom	✅	pdf.js fallback.
Layer panel	✅ if PDF has OCGs	pdf.js fallback.
Color picker	✅	RGB only (no TAC).
Measure tool	✅	Page dimensions from PDF.
Separations	❌ hidden	Needs a backend; pdf.js renders RGB only.
Densitometer	❌ hidden	Same.
TAC heatmap	❌ hidden	Same.
Annotations	❌ hidden	Needs persistence.
Report links	❌ hidden	Needs a backend.

Pass services to wire the backend-dependent ones. The reference server in server/ is a turnkey option — see server.md.

Slot props

Slot props let you replace individual regions without reimplementing the entire viewer. Each slot accepts a static ReactNode or a render function that receives the current LensPDFViewerState:

import { LensPDFViewer } from "@printwithsynergy/lens-pdf/components";

<LensPDFViewer
  pdfUrl={url}
  header={(state) => (
    <div>
      <span>Page {state.currentPage}</span>
      <button onClick={() => state.setZoom(state.zoom + 25)}>Zoom in</button>
    </div>
  )}
  footer={<p>Powered by LensPDF</p>}
/>

LensPDFViewerState exposes: zoom, setZoom, currentPage, setCurrentPage, pageCount, activeTool, setActiveTool, enabledLayers, toggleLayer, setAllLayers, hasLayers, layersOpen, setLayersOpen.

Custom layouts

<LensPDFViewer> is purely additive. The lower-level surface stays exactly as before — for bespoke layouts compose PageCanvas, LayerPanel, MeasureTool, ColorPickerTool, etc. with your own context providers. See components.md for the per- component reference.

Other integration tiers

• Less boilerplate — <LensPDFDemo> bakes in upload, URL paste, drag-drop, and validation. ~5 lines.
• More control — useLensPDF() + <LensPDFProvider> manage state while you build the layout.
• Full custom — wire ViewerHostContext + ViewerServicesContext yourself. See architecture.md.

Security

The pdfUrl you pass is fetched verbatim by the user’s browser. If a user shouldn’t be able to read that PDF, the host must enforce that upstream — sign the URL, scope it, expire it. The viewer is a pure renderer and doesn’t authenticate anything.

The pdf.js worker is loaded from unpkg by default. For deployments that can’t reach unpkg (intranet, air-gapped CI, strict CSPs), set workerSrc to a self-hosted URL or import the worker into your app’s build and pass its bundler-resolved URL.