Rocket.Chat 8.5 @rocket.chat/apps deno-runtime main.ts package path
After Rocket.Chat upgrades, a cached or generated runtime pointer may still target the old apps-engine runtime path even though the installed package now exposes the runtime under `@rocket.chat/apps`.
Agent Quick Fix
# Replace stale pointer:
# node_modules/@rocket.chat/apps-engine/deno-runtime/main.ts
# With current package runtime:
node_modules/@rocket.chat/apps/deno-runtime/main.tsRecreate the stale symlink or generated pointer, then restart Rocket.Chat so the apps engine loads the current runtime entry.
Symptom
Marketplace apps or built-in app integrations fail with `Module not found` around `/tmp/apps-engine-temp/deno-runtime/main.ts`, while the install contains `@rocket.chat/apps` and no matching `@rocket.chat/apps-engine/deno-runtime` tree.
Why This Happens
The local pointer survived an upgrade across a package layout change. The installed artifact moved, but the generated runtime path still names the old package.
Codex Search Keywords
Rocket.Chat 8.5 @rocket.chat/apps deno-runtime main.ts package path
"@rocket.chat/apps" "deno-runtime"
npm "@rocket.chat/apps" "deno-runtime"
https://registry.npmjs.org/@rocket.chat%2fapps
GitHub Rocket.Chat "@rocket.chat/apps" "package.json"Source Trail
GitHub source search: Rocket.Chat @rocket.chat/apps deno-runtime