Bug
streamPdfFile calls validateParameters (which validates and returns a concurrency value) but never uses the returned value. The streaming implementation always processes pages sequentially in a plain for loop regardless of the concurrency option passed by the caller.
Affected code
src/core.ts — streamPdfFile and its public wrappers (streamPdf2image, streamPdf2string, streamPdf2mixed).
Failure scenario
A caller passes { concurrency: 4 } to streamPdf2image expecting parallel page processing. The option passes validation with no error, but all pages still process one at a time. No warning is emitted and throughput is identical to concurrency: 1.
Options
- Implement parallelism in the streaming path (yield results in order, process pages in parallel).
- Reject the option with an error or warning when passed to the streaming API.
- Document that
concurrency has no effect on the streaming API (least work, but still silently misleading).
Bug
streamPdfFilecallsvalidateParameters(which validates and returns aconcurrencyvalue) but never uses the returned value. The streaming implementation always processes pages sequentially in a plainforloop regardless of theconcurrencyoption passed by the caller.Affected code
src/core.ts—streamPdfFileand its public wrappers (streamPdf2image,streamPdf2string,streamPdf2mixed).Failure scenario
A caller passes
{ concurrency: 4 }tostreamPdf2imageexpecting parallel page processing. The option passes validation with no error, but all pages still process one at a time. No warning is emitted and throughput is identical toconcurrency: 1.Options
concurrencyhas no effect on the streaming API (least work, but still silently misleading).