npm / @aiden0z/pptx-renderer
@aiden0z/pptx-renderer
What changed in @aiden0z/pptx-renderer 1, from its official release notes, upgrade guides and advisories. Sources checked 2026-10-28.
1 security3 new APIs and options2 performance6 behavior and defaults1 tooling26 fixes and other
See which of these apply to your code, ranked, in your agent:
npx @unstale/cli init@aiden0z/pptx-renderer 139 changes
Security 1
Untrusted CSS and SVG path values use bounded parsing paths instead of unsafe backtracking parsing.
New APIs and options 3
Adds host control over external media requests on PptxViewer, the compatibility renderer, thumbnails, and standalone renderSlide(). The default is allow; block prevents loading external media relationships.
Validated ordinary-shape reflections are now supported.
A standalone ESM entry enables direct browser use without an application bundler.
Performance 2
Asynchronous media cleanup has been improved.
The standalone browser bundle includes only the renderer's supported chart surface, without changing default animation behavior.
Behavior and default changes 6
Serialized presentations now include typed layout/master template shapes and each slide's layoutPath, masterPath, and showMasterSp references.
Compatible-content selection has been improved.
Embedded EOT/MTX fonts can now be loaded for rendering.
Browser rendering now supports a bounded subset of common equations, with package-authored fallback content for unsupported formula trees.
Rendering adds bounded support for selected combinations of bevel, camera-plane, picture, text, custom-geometry, and group content.
SVG and OLE preview rendering has been improved.
Tooling 1
Visual evaluation now has reproducible browser, font, PPTX, ground-truth, and renderer provenance.
Fixes and other changes 26
Honors chart label number formats and point-level source-linked resets, reserves bottom legend space, and improves automatic positive-axis bounds.
Respects cNvPr@hidden on slides, layouts, masters, OLE previews, and nested groups; hidden content no longer starts media loading.
Positions preset-shape text in the standard DrawingML text rectangle while preserving explicit text transforms, adjusted geometry, group coordinates, and degenerate-guide fallbacks.
Authored visibility metadata is retained in serialized output even when a node is not rendered.
Improves text tabs, terminal hanging punctuation, vertical text, picture-filled runs, and placeholder style inheritance.
Samples backgrounds in slide coordinates before clipping to shape geometry, covering 2D transforms, inherited backgrounds, lazy images, and the default white background; template shapes use their master/layout background chain.
Measures wrapped line height for autofit while preserving existing CJK wrapping and spacing behavior.
Chart defaults and layout, combo and secondary-axis cases, sparse and literal data sources, explicit zeros, and negative-value behavior are improved.
CJK text wrapping has been improved.
Clipped picture effects have been improved.
A pinned geometry runtime renders all 28 zero-adjustment flowcharts and supports bounded donut adjustments.
Group transform rendering has been improved.
Office percentage spacing has been improved.
Validated ordinary-shape outer shadows are now supported.
Paragraph edge rendering has been improved.
Placeholder and color-map inheritance has been improved.
Selected spAutoFit growth cases are now handled more accurately.
Rendering of styled soft breaks has been improved.
Common table styles, merges, cell margins and anchors, conditional borders, and direct cell overrides are handled better.
Text color precedence has been improved.
Compact no-wrap text runs no longer create horizontal scrollbars in narrow text boxes.
Applications with a restrictive CSP that enable EMF-PDF fallback must allow the configured PDF.js module source and blob Workers.
Mixed horizontal and vertical overflow settings no longer turn elements into browser scroll containers.
Late fallback results no longer mutate disposed slide DOM or repopulate revoked media caches.
Loading-task cleanup and Worker termination are fixed across success, failure, timeout, and cancellation paths.
PDF.js remains optional and can be self-hosted by applications that need EMF-PDF fallback rendering.