<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Nodejs on blog.marcinkowski.ca</title>
		<link>https://blog.marcinkowski.ca/tags/nodejs/</link>
		<description>Recent content in Nodejs on blog.marcinkowski.ca</description>
		<generator>Hugo</generator>
		<language>en-ca</language>
		
		
		
		
			<lastBuildDate>Mon, 11 Aug 2025 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://blog.marcinkowski.ca/tags/nodejs/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>PDFs and Node in 2025: A Comprehensive Guide to Rendering and Parsing</title>
				<link>https://blog.marcinkowski.ca/posts/2025/08/11/pdfs-and-node-in-2025/</link>
				<pubDate>Mon, 11 Aug 2025 00:00:00 +0000</pubDate>
				<guid>https://blog.marcinkowski.ca/posts/2025/08/11/pdfs-and-node-in-2025/</guid>
				<description>&lt;h1 id=&#34;pdfs-and-node-in-2025-a-comprehensive-guide-to-rendering-and-parsing&#34;&gt;PDFs and Node in 2025: A Comprehensive Guide to Rendering and Parsing&lt;/h1&gt;&#xA;&lt;p&gt;As we move through 2025, the Node.js ecosystem continues to evolve with powerful tools for working with PDFs. Whether you need to generate new PDF documents, parse existing ones, or manipulate their content, there are several mature libraries available. In this post, I&amp;rsquo;ll explore three prominent PDF libraries and provide a comprehensive comparison of their capabilities.&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-current-landscape&#34;&gt;The Current Landscape&lt;/h2&gt;&#xA;&lt;p&gt;PDF processing in Node.js has matured significantly over the past few years. We now have libraries that can handle everything from simple text extraction to complex document manipulation, all while maintaining good performance and developer experience.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
