Repository navigation
[runtime] apify call fails if the TS project was not built outside the runtime #1461
Description
After connecting to the runtime and performing apify push, the Run fails immediately because the Actor was never built locally:
2026-09-24T14:18:35.295Z [actor-runtime] Live dev folder: /Users/me/myactor (mounted over the image's working directory /usr/src/app; node_modules preserved via a per-run volume)
2026-09-24T14:18:35.295Z [actor-runtime] !! Running in `Live dev folder mode`: this run uses the local source files above, mounted over the
2026-09-24T14:18:35.295Z [actor-runtime] !! built Docker image. TS-based Actors require local compilation (e.g. `npm run build`) before the run.
2026-09-24T14:18:35.295Z [actor-runtime] !! To run purely from the built Docker image, use `apify call --no-dev-folder`.
2026-09-24T14:18:35.823Z node:internal/modules/cjs/loader:1568
2026-09-24T14:18:35.823Z throw err;
2026-09-24T14:18:35.823Z ^
2026-09-24T14:18:35.823Z
2026-09-24T14:18:35.823Z Error: Cannot find module '/usr/src/app/dist/main.js'
2026-09-24T14:18:35.823Z at Module._resolveFilename (node:internal/modules/cjs/loader:1564:15)
2026-09-24T14:18:35.823Z at wrapResolveFilename (node:internal/modules/cjs/loader:1118:27)
2026-09-24T14:18:35.823Z at defaultResolveImplForCJSLoading (node:internal/modules/cjs/loader:1142:10)
2026-09-24T14:18:35.823Z at resolveForCJSWithHooks (node:internal/modules/cjs/loader:1169:12)
2026-09-24T14:18:35.823Z at Module._load (node:internal/modules/cjs/loader:1341:5)
2026-09-24T14:18:35.823Z at wrapModuleLoad (node:internal/modules/cjs/loader:261:19)
2026-09-24T14:18:35.823Z at Module.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:154:5)
2026-09-24T14:18:35.823Z at node:internal/main/run_main_module:33:47 {
2026-09-24T14:18:35.823Z code: 'MODULE_NOT_FOUND',
2026-09-24T14:18:35.823Z requireStack: []
2026-09-24T14:18:35.823Z }
2026-09-24T14:18:35.823Z
2026-09-24T14:18:35.823Z Node.js v24.21.0
This is because apify call mounts the current directory by default.
Maybe the CLI could detect that the build folder is missing and warn the user.
Activity
l2ysho commentedon Sep 24, 2026
@Pijukatel assigned to you as it is actor-runtime related
Pijukatel commentedon Sep 25, 2026
The log already contains hints about this error:
I will make it even more explicit to make sure users understand what is wrong.
Pijukatel commentedon Sep 30, 2026
Latest cli from apify@runtime +
apify runtime install, will fetch the latest version of the runtime with more explicit logs and dev folder being registered by default but not saved unless confirmed to avoid confusion.https://github.com/apify/actor-runtime/releases/tag/v0.1.1