Solution skill
Pass a Buffer directly as the Mindee Node SDK input source
Complete solution
Shows how to fix pass a Buffer directly as the Mindee Node SDK input source. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
The maintainer agreed Buffer input made sense and shipped it in v3.1.1. Buffer input sources landed in v3.1.1, so upgrade and pass the Buffer straight in.
Steps
- Issue mindee/mindee-api-nodejs#101 (closed, 5 comments): the reporter generated PDFs with pdf-lib as a Buffer and had to hex-encode before uploading, which was wasteful since the SDK decoded it back. The maintainer agreed Buffer input made sense and shipped it in v3.1.1.
- You dont need to hex-encode a Buffer before sending it to the Mindee Node SDK anymore. Buffer input sources landed in v3.1.1, so upgrade and pass the Buffer straight in. If you are pinned to an older version, the hex round-trip is the workaround, but upgrading is the real fix.
When to use
You are seeing this: Issue mindee/mindee-api-nodejs#101 (closed, 5 comments): the reporter generated PDFs with pdf-lib as a Buffer and had to hex-encode before uploading, which was wasteful since the SDK decoded it back. Use this skill when you run into "Pass a Buffer directly as the Mindee Node SDK input source".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
Versions mentioned in the source: v3.1.1. If you are on something much newer or older, the details may have shifted.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Evidence
In gh:mindee/mindee-api-nodejs#101 (Mindee), the issue reported was: Issue mindee/mindee-api-nodejs#101 (closed, 5 comments): the reporter generated PDFs with pdf-lib as a Buffer and had to hex-encode before uploading, which was wasteful since the SDK decoded it back. The maintainer agreed Buffer input made sense and shipped it in v3.1.1. The verified resolution from the thread: You dont need to hex-encode a Buffer before sending it to the Mindee Node SDK anymore. Buffer input sources landed in v3.1.1, so upgrade and pass the Buffer straight in. If you are pinned to an older version, the hex round-trip is the workaround, but upgrading is the real fix. Source: mount the host path https at container path //github.com/mindee/mindee-api-nodejs/issues/101
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_EwrkTQrCh_prEGQ69Hpeog" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Pass a Buffer directly as the Mindee Node SDK input source <span>— Vectle</span></a>