[dbartholomae]

Fixes #3570

What

@react-pdf/font loads each standard font's metrics through a dynamic import('pdfkit/standard-fonts/<Name>') the first time a document uses that face, and hands them to pdfkit through registerStdFonts before it opens the font. The static specifiers let a bundler carry the metrics along, and the dynamic import keeps them lazy in both the Node and the browser build. The browser build no longer registers all fourteen fonts at import.

@react-pdf/renderer awaits the font store's Helvetica load before it creates its PDFDocument, because pdfkit opens Helvetica in the document constructor, before any layout has loaded a font.

Why

pdfkit's Node build reads standard font metrics from a file beside its own module on first use. Bundled into another file it looks next to that file and finds nothing, and the Cannot find module '#standard-fonts/Helvetica' in #3570 is the result. The fix in the issue was to keep pdfkit external, which works but is a workaround for a package that otherwise bundles fine.

Depends on

pdfkit's Node build only exports registerStdFonts from the release that carries foliojs/pdfkit#1802 on. The code reads the export from the module namespace and does nothing when it is missing, so this is mergeable against pdfkit 0.20.x now: unbundled, pdfkit's own file loaders keep working as before, and the bundled case starts working once the pin moves to a pdfkit release that has the export. #3550 bumps the pin to 0.20.2, which does not yet have it.

Note for consumers: Font.getFont() for a standard font now returns data: null until Font.load() for that face has resolved, the same as for a registered font file.

Checked

• packages/font, packages/layout and packages/renderer tests, the font package typecheck and build, eslint and prettier pass.
• A new packages/font/tests/standard-font.test.ts covers registering a face on first use, not registering unused faces, and registering a face once over repeated loads.
• An esbuild bundle of @react-pdf/renderer from this branch against a pdfkit build that carries Let the Node build be bundled: export registerStdFonts, resolve standard fonts and the ICC profile on first use foliojs/pdfkit#1802 renders a document with text and a document without text, in ESM and CommonJS output. The same bundle against published pdfkit fails with the error from Node build can't render once bundled: pdfkit reads its standard fonts from disk next to its own module #3570, as expected.

Written with Claude Code, an AI assistant; the change was designed and verified in our own bundles as described above.

[changeset-bot]

🦋 Changeset detected

Latest commit: 03b1c05

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 11 packages

Name	Type
@react-pdf/font	Patch
@react-pdf/renderer	Patch
@react-pdf/types	Patch
@react-pdf/math	Patch
@react-pdf/mermaid	Patch
@react-pdf/ui	Patch
@react-pdf/examples	Patch
@react-pdf/layout	Patch
@react-pdf/render	Patch
@react-pdf/stylesheet	Patch
@react-pdf/tailwind	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

@dbartholomae is attempting to deploy a commit to the diegomura Team on Vercel.

A member of the Team first needs to authorize it.