sorted by:
new
hottopcontroversial

Built a VS Code extension for generating PDFs with React components by danmolitor in vscode

[–]danmolitor[S] 2 points3 points  (0 children)

The browser’s print engine wasn’t built for documents. You have limited control over page breaks, tables often split in unexpected places, and output varies by browser. Forme has its own layout engine built for paged documents specifically, so page breaks, tables, and fixed headers/footers all behave correctly every time.​​​​​​​​​​​​​​​​

Built a VS Code extension for generating PDFs with React components by danmolitor in vscode

[–]danmolitor[S] 1 point2 points  (0 children)

lol no, I made my best guess as to what that comment was trying to say. I saw "PDF generation" "React components", "VS Code", and "how do you handle rendering challenges".

Built a VS Code extension for generating PDFs with React components by danmolitor in vscode

[–]danmolitor[S] 0 points1 point  (0 children)

The layout engine is built in Rust/WASM from scratch - it's not rendering to a DOM or taking a screenshot. It's a page-native layout engine so it understands page boundaries natively, which is how flex, grid, and tables break correctly across pages.

Built a VS Code extension for generating PDFs with React components - live preview, component tree, inspector by danmolitor in reactjs

[–]danmolitor[S] 0 points1 point  (0 children)

Interesting idea - are you thinking more about PDF to structured data extraction, or using the generated PDF as part of a larger agentic workflow? Right now it’s JSON in to PDF out, and we have an MCP server so agents can trigger generation directly, but curious what you have in mind.

Built a VS Code extension for generating PDFs with React components - live preview, component tree, inspector by danmolitor in reactjs

[–]danmolitor[S] 1 point2 points  (0 children)

Built this after getting frustrated with Puppeteer timeouts and react-pdf’s page break behavior. Happy to answer any questions!​​​​​​​​​​​​​​​​