fix(typst-preview): use RenderByContentOptions to avoid Rust aliasing

Replace runWithSession + manipulateData + session.renderToSvg with the direct RenderByContentOptions form: renderer.renderToSvg({ format: 'vector', artifactContent, container }). The session-based API kept hitting 'recursive use of an object detected which would lead to unsafe aliasing in rust' because runWithSession holds a mutable borrow of the session while renderToSvg also takes one — regardless of whether you call renderer.renderToSvg({ renderSession }) or session.renderToSvg(). The content-based form creates and disposes the session internally without any caller-visible borrow. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-06-19 15:22:56 +00:00
parent c6d71e58b7
commit eedf4b50f6
1 changed files with 6 additions and 5 deletions
@@ -71,11 +71,12 @@ const TypstWasmPreview: FC = () => {
      dataToRender = null

      try {
-        await renderer.runWithSession(async session => {
-          session.manipulateData({ action: 'reset', data })
-          // Use session.renderToSvg (NOT renderer.renderToSvg with renderSession)
-          // to avoid double-aliasing the same Rust object inside runWithSession
-          await session.renderToSvg({ container })
+        // Use RenderByContentOptions: pass artifactContent directly instead of
+        // using runWithSession + manipulateData, which causes Rust aliasing errors
+        await renderer.renderToSvg({
+          format: 'vector',
+          artifactContent: data,
+          container,
        })
        pendingVectorRef.current = null
        setStatus('ready')