Index out of bounds when performing removePage action

[gonuit]

pdf-lib 1.0.0

Uncaught (in promise) Error: Index out of bounds: 1/1
    at PDFPageTree.removeLeafNode (PDFPageTree.js:95)
    at PDFCatalog.removeLeafNode (PDFCatalog.js:33)
    at PDFDocument.removePage (PDFDocument.js:244)
    at PagesDisplayer.handleDownload (pages_displayer.tsx:71)
    at HTMLUnknownElement.callCallback (react-dom.development.js:147)
    at Object.invokeGuardedCallbackDev (react-dom.development.js:196)
    at invokeGuardedCallback (react-dom.development.js:250)
    at invokeGuardedCallbackAndCatchFirstError (react-dom.development.js:265)
    at executeDispatch (react-dom.development.js:571)
    at executeDispatchesInOrder (react-dom.development.js:596)
    at executeDispatchesAndRelease (react-dom.development.js:695)
    at executeDispatchesAndReleaseTopLevel (react-dom.development.js:704)
    at forEachAccumulated (react-dom.development.js:676)
    at runEventsInBatch (react-dom.development.js:844)
    at runExtractedEventsInBatch (react-dom.development.js:852)
    at handleTopLevel (react-dom.development.js:5029)
    at batchedUpdates$1 (react-dom.development.js:21463)
    at batchedUpdates (react-dom.development.js:2247)
    at dispatchEvent (react-dom.development.js:5109)
    at react-dom.development.js:21520
    at Object.unstable_runWithPriority (scheduler.development.js:255)
    at interactiveUpdates$1 (react-dom.development.js:21519)
    at interactiveUpdates (react-dom.development.js:2268)
    at dispatchInteractiveEvent (react-dom.development.js:5085)

[Hopding]

Hello @gonuit!

Based on the stacktrace you shared, it looks like you are trying to call pdfDoc.removePage(1) on a document with only a single page. In v1.0.0, you must use zero-based indexes. So you’ll have to call pdfDoc.removePage(0).

If this doesn’t work, then I’ll need to see some sample code that I can use to reproduce the issue.

I hope this helps. Let me know if you have any additional questions!

[Hopding]

@gonuit Please see the discussion in #150 (comment). Also, if you update to v1.0.1, you should see a different (more understandable) error message.