fix(generator): resolve kompendium.json symlink to an absolute path

[adrianschmidt]

What

In watch mode the docs generator symlinks the public kompendium.json (under publicPath, e.g. www/) to the real file in the config folder (under path, e.g. .kompendium/). The link was created with a relative source:

await symlink(`${config.path}/kompendium.json`, `${config.publicPath}/kompendium.json`);
// symlink(".kompendium/kompendium.json", "www/kompendium.json")

A relative symlink target is resolved relative to the link's own directory (www/), not the cwd — so www/kompendium.json points to the nonexistent www/.kompendium/kompendium.json. The result is a broken link and a 404 for the docs data on every dev-server reload.

Fix

Resolve the source to an absolute path so the link is valid regardless of its location:

await symlink(resolve(source), target);

Keeps the native fs.symlink — does not reintroduce the lnk → rimraf@2 → glob@7 dependency chain that was deliberately removed.

Background

The regression was introduced by the lnk → fs.symlink swap in jgroth#183 (update-deps), which reached lime as 1359554 and shipped in published 1.2.0. Versions ≤ 1.1.2 used lnk(...) and were unaffected. The same one-line fix has also been pushed to the upstream update-deps branch (jgroth#183).

Verification

• npm run build ✅ (generator compiles)
• Confirmed empirically that an absolute www/kompendium.json symlink resolves to the 5 MB docs file, where the relative one was broken.