Fdk pack -s fails with "Error while generating digest file" (FDK 10.1.8, Node v24.11.0)

Krishna_M · July 29, 2026, 6:48am

Hi team,

I’m hitting a digest generation failure when packing my app. The webpack build itself completes successfully, but packing fails right after with no further detail.

Environment:
FDK version in manifest: 10.1.2 (auto-updated to 10.1.8 on run)
FDK version installed/running: 10.1.8
Node version: v24.11.0
Command: fdk pack -s

Log output:
FDK version mismatch. App was developed in 10.1.2 and is being run in 10.1.8.
FDK version in manifest is being updated to the current version.
Starting local server to test app settings validation
App setting validation probe success
App being packed in Node v24.11.0 using FDK 10.1.8
Code coverage has been skipped. Skipping code coverage may result in your app being rejected by the Freshworks Marketplace.
[… webpack build output, compiled successfully …]
webpack 5.105.4 compiled successfully in 6517 ms
Error while generating digest file.

App setting validation passes and the webpack build compiles cleanly with all assets emitted (vendors, main, runtime bundles + index.html), so the failure appears to happen specifically in FDK’s post-build digest/packaging step, not in my app code.

What I’ve tried:
Confirmed webpack output completes with no errors
App settings validation passes locally

Questions:
Is FDK 10.1.8 known to have issues generating the digest file on Node v24.x? I noticed earlier threads on this error were traced to Node version constraints on older FDK releases — is there a currently supported/recommended Node version for FDK 10.1.8?
Could the automatic manifest FDK-version bump (10.1.2 → 10.1.8) be leaving the manifest in a state that breaks digest generation?
Any way to get more verbose/debug output from fdk pack to see exactly where digest generation is failing?

Thanks!

Himanshu_Sharma · August 5, 2026, 7:39am

Hi @Krishna_M ,your setup (Node v24.11.0 + FDK 10.1.8) is the supported stack for FDK 10.x. This is unlikely a Node-version mismatch like the older FDK 9 threads.

The manifest bump 10.1.2 → 10.1.8 is normal and should not break digest generation on its own. Commit the updated engines.fdk after pack.

What’s likely happening

Webpack finishing only means the frontend build succeeded. Digest generation runs after that - FDK hashes app files into digest.md5 (and related report hashes). Failures here are usually environment or artifact-related, not app logic.

1. Get verbose logs

NODE_DEBUG=fdk fdk pack -s

Also check log/fdk.log in your app directory - it often shows the exact file that failed (e.g. Computing digest for manifest.json or Generating hash for report.json).

2. Clean stale artifacts, then repack

rm -rf dist/ coverage/ digest.md5 .report.json
fdk validate
fdk pack -s

FDK 10.1+ validates that .report.json (from prior fdk run) isn’t modified/deleted mid-pack. A stale or locked file can cause pack failures.

3. Common causes (webpack / meta-framework apps)

Cause	Fix
Stale `digest.md5` in app root	Delete before pack
File watcher / IDE saving during pack	Close watchers; repack
`dist/` or webpack cache conflicts	Remove `dist/`, `.cache/`, re-pack
FDK upgrade without clean install	Reinstall FDK 10.1.8 cleanly
Path/permission issues (esp. Windows)	Pack from a simple local path

4. Pin manifest engines (optional but good practice)

"engines": {
  "node": "24.11.0",
  "fdk": "10.1.8"
}