The fs.rmdir → fs.rm change in #8 fixes the crash on newer Node:
The property 'options.recursive' is no longer supported. Received true
It's in main, but it never made it to npm. The publish workflow failed: https://github.com/divizend/ghostscript-node/actions/runs/21139190379/job/60788599535
So latest on npm is still 1.5.0 from 2023, and that tarball's dist/index.js still has the old fs.rmdir(outDir, { recursive: true }). Anyone installing from npm keeps hitting the crash even though the source is fixed.
On Node 26 this throws instead of just warning, so every renderPDFPagesToPNG call fails regardless of the PDF, since the failing line is temp-dir cleanup after the render.
Could the release be re-run or a new version published?
The
fs.rmdir → fs.rmchange in #8 fixes the crash on newer Node:It's in
main, but it never made it to npm. The publish workflow failed: https://github.com/divizend/ghostscript-node/actions/runs/21139190379/job/60788599535So
lateston npm is still1.5.0from 2023, and that tarball'sdist/index.jsstill has the oldfs.rmdir(outDir, { recursive: true }). Anyone installing from npm keeps hitting the crash even though the source is fixed.On Node 26 this throws instead of just warning, so every
renderPDFPagesToPNGcall fails regardless of the PDF, since the failing line is temp-dir cleanup after the render.Could the release be re-run or a new version published?