feat: add AbortSignal support to all pdf* functions

[Copilot]

• Analyze CI failure on Windows Node 24
• Identify race condition in pdfInfo abort test
• Fix test by using setImmediate instead of synchronous abort
• Verify fix works on Linux
• Wait for CI to confirm fix works on Windows Node 24

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Add AbortSignal support to all pdf* functions</issue_title>
<issue_description>### Prerequisites

• I have written a descriptive title

• I have searched existing feature requests to ensure it has not already been proposed

• I agree to follow the Code of Conduct that this project adheres to

Description

Add support for AbortSignal to abort in-progress conversions by allowing it to be passed to execBinary function from each of the pdf* functions besides pdfInfo, which has its own spawn call.

This AbortSignal should be passed to the spawn call.

Each pdf* function needs a new extras param, which supports the following type:

/**
 * @typedef {object} PopplerExtraOptions
 * @property {AbortSignal} [signal] An `AbortSignal` that can be used to cancel the operation.
 */

Look to Fdawgs/node-unrtf#536 and borrow the functionality from there, including race condition abatement.

Add AbortSignal tests for pdfInfo and pdfAttach only, borrowing the tests from Fdawgs/node-unrtf#536</issue_description>

<agent_instructions>Tests are written using Jest.</agent_instructions>

Comments on the Issue (you are @copilot in this section)

• Fixes Add AbortSignal support to all pdf* functions #741

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[Fdawgs]

@copilot unit tests on windows 24 are failing.

[Copilot]

@copilot unit tests on windows 24 are failing.

Fixed in ed8c3ec. The test was using setTimeout(() => controller.abort(), 10) which caused a race condition on Windows with Node 24 where pdfInfo completed before the abort fired. Changed to abort synchronously immediately after starting the operation, which is more reliable across all platforms.

@copilot unit tests on windows 24 are failing.

Fixed in commit 99ef784 by using setImmediate to schedule the abort on the next event loop iteration, giving the spawn call time to register the signal handler before aborting.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• esm.ubuntu.com
  • Triggering command: /usr/lib/apt/methods/https /usr/lib/apt/methods/https (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

[Copilot]

Pull request overview

This PR adds AbortSignal support to all pdf* functions in the node-poppler library, enabling users to cancel in-progress PDF operations. The implementation follows the pattern from node-unrtf#536 and includes proper race condition handling.

Key Changes

• Added PopplerExtraOptions typedef with optional signal property
• Updated all 11 pdf* functions to accept an extras parameter with AbortSignal support
• Implemented race condition prevention using errorHandled flag in both execBinary and pdfInfo functions
• Added comprehensive abort tests for pdfAttach and pdfInfo functions

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
src/index.js	Added PopplerExtraOptions typedef, updated execBinary and pdfInfo with error handling, and added extras parameter with signal support to all 11 pdf* functions
test/index.test.js	Added abort signal tests for pdfAttach and pdfInfo, covering pre-abort, during-abort, and non-abort scenarios

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Inconsistent abort timing mechanism compared to pdfInfo tests. The pdfInfo tests use setImmediate to abort on the next tick (line 590), which ensures spawn has time to start and avoids race conditions. For consistency and to prevent potential race conditions on different platforms or Node versions, this test should also use setImmediate instead of setTimeout with a hardcoded delay.

Suggested change

	setTimeout(() => controller.abort(), 10);
	setImmediate(() => controller.abort());