Repository navigation
MicroPrint 1.3.3 – Reliable Label Scaling & API Cleanup
-
Reliable label shrink‑to‑fit
- All label prints now go through SumatraPDF with
paperkind=256,shrink, matching the known‑good CLI behavior. - Applies to both URL (
POST /print-url) and base64 (POST /print-data) label flows.
- All label prints now go through SumatraPDF with
-
Consistent across dev and installed builds
- New resolveSumatraPath() helper locates Sumatra from:
- Dev:
node_modules\pdf-to-printer\dist\SumatraPDF-3.4.6-32.exe - Packaged app:
resources\app.asar.unpacked\node_modules\pdf-to-printer\dist\SumatraPDF-3.4.6-32.exe - Plus standard
Program Files\SumatraPDF\SumatraPDF.exelocations.
- Dev:
- New resolveSumatraPath() helper locates Sumatra from:
-
Label options simplified
- For
documentType: "label", APIscale/paperSizeare ignored; labels always use a fixed shrink‑to‑fit label mode. - Invoices and generic PDFs still honor
scale(noscale/shrink/fit) andpaperSize.
- For
-
API surface and docs cleanup
- Removed legacy and unused endpoints:
/print,/print-both/pdf-list,/sample-pdfs/api/status,/history,/stats,/api-docs,/api-examples,/status-check,/test
- api-docs.html now documents only:
POST /print-url,POST /print-dataGET /printers,GET /settings,POST /settingsGET /status,GET /print-history,GET /statistics
- Docs explicitly note that labels always use
paperkind=256,shrinkinternally.
- Removed legacy and unused endpoints: