Roadmap 0.11, Fixes

FX.390 SuperCad Studio: PDFs did not open ("Setting up fake worker failed"): the packed panels asked for a PDF reader file under its old name

  • Fix
  • Built · in the lab
  • SuperCad Studio

Reported on Discord #supercad-studio (a Discord member, 2026-11-19) on SuperCad Studio 0.10.1 for Windows: opening a PDF gave "Setting up fake worker failed: Failed to fetch dynamically imported module: http://cadcraft.localhost/assets/vendor/pdfjs/6.3.289/build/pdf.worker.min.mjs". Nothing went to the internet: cadcraft.localhost is the app's own files on that computer. The edition packer renames every .mjs library file to .js and rewrites the references, but SuperCad's per-app panel payloads (assets/apps/supercadcraft/<x.y>/payload/<app>.json, written after that step by devshell/edition-super.php) kept the app manifest's name pdf.worker.min.mjs, a file the build does not have. So every PDF path inside SuperCad failed: MarkupCraft, TakeoffCraft, CadCraft and BimCraft underlays, CivilCraft scans. The eight single apps and CadCraft Studio (the suite) were not affected. Fixed in devshell/edition-super.php + edition.php: payloads get the same .mjs to .js rename, their data-* addresses (PDF and OCR files) are made relative like the single editions so the browser edition also runs from a sub-folder, and the packer now stops when a payload names a renamed file or keeps an absolute data address. Checked: 0.10.1 repacked with the fix; a headless browser opens a PDF with each of three payloads' addresses (shipped build: the same error as the report). Not done: no new SuperCad Studio build has been made or published, and the fix was not run in the Windows app itself. People on 0.10.1 need a new build.

From: Discord community

Add a comment

Community comments

No comments yet

Add detail as we go: how you would use it, files or steps that show the problem, what other programs do. The team reads every comment.

Sign in or create a free account to add a comment.