fix(docker): need workspace packages for execution worker

[icecrasher321]

Summary

Need to copy over workspace packages (e.g. sim logger for exec worker)

Type of Change

• Bug fix

Testing

In progress.

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview, Comment	Mar 28, 2026 1:52am

[cursor]

PR Summary

Low Risk
Low risk: a Docker packaging-only change that affects runtime image contents, with main impact being image size and worker startup behavior if dependencies were previously missing.

Overview
Fixes the runtime Docker image so the bundled BullMQ execution worker can resolve its workspace dependencies.

In docker/app.Dockerfile, the runner stage now copies the monorepo packages/ directory alongside apps/sim/dist/worker.cjs, ensuring shared internal packages (e.g., logger) are available at runtime.

^{Written by Cursor Bugbot for commit f6656d2. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

[cursor]

Entire packages directory copied instead of needed package

Low Severity

The COPY directive brings the entire packages directory into the runtime image, but only @sim/logger is needed by the worker. This unnecessarily includes packages/db (with 180+ SQL migration files and admin scripts like seed-stress-test-users.ts), packages/python-sdk, packages/cli, packages/testing, packages/ts-sdk, and packages/tsconfig — none of which are required at runtime. Copying only packages/logger would keep the image lean.

 

[greptile-apps]

Greptile Summary

This PR adds a COPY --from=builder /app/packages ./packages instruction to the runner stage of the Docker image so that the BullMQ execution worker can resolve @sim/logger at runtime. The worker is built with --packages=external, which means @sim/logger is not inlined into worker.cjs and must be present on the module-resolution path at startup.

Key observations:

• Every processor file in apps/sim/worker/ imports exclusively from @sim/logger — no other workspace package is needed by the worker
• The entire packages tree is being copied, including packages/db (SQL migrations, Drizzle config), packages/testing (test utilities), packages/cli, and packages/ts-sdk — none of which are used by the worker and should not be shipped in a production runner image
• Whether the fix is sufficient depends on whether node_modules/@sim/logger is present in the runner after the standalone copy; if Next.js's trace-based standalone bundler omits @sim/logger (because it is only used by the worker, not by Next.js pages/API routes), copying packages/logger alone does not create the missing node_modules entry and the require('@sim/logger') call in worker.cjs would still fail at startup

Confidence Score: 3/5

Hold for verification — the fix's effectiveness depends on node_modules symlink/standalone-trace behaviour that isn't confirmed, and the copy scope includes production-inappropriate artifacts

A P1 concern exists: the bare require('@sim/logger') in worker.cjs resolves only via node_modules, not via the raw packages/ directory copy. If @sim/logger is absent from the standalone output's node_modules, the worker will still crash on startup. Additionally, the entire packages tree — including DB migration files and test utilities — is unnecessarily included in the production image.

docker/app.Dockerfile — specifically the scope of the COPY and whether node_modules/@sim/logger is present in the runner

Important Files Changed

Filename	Overview
docker/app.Dockerfile	Adds COPY of entire /packages tree to the runner stage so @sim/logger is available to worker.cjs; correctly identifies the root cause but the approach copies unnecessary packages (db, testing, cli, ts-sdk) and may not fully solve the module-resolution problem if node_modules/@sim/logger doesn't already exist in the runner's node_modules path.

Sequence Diagram

sequenceDiagram
    participant Builder as Builder Stage
    participant Standalone as .next/standalone
    participant Runner as Runner Stage
    participant Worker as worker.cjs (runtime)

    Builder->>Standalone: next build (traces deps, copies node_modules)
    note over Standalone: May or may not include<br/>node_modules/@sim/logger<br/>(depends on standalone tracer)

    Builder->>Runner: COPY .next/standalone → /app
    note over Runner: /app/node_modules/ from standalone
    Builder->>Runner: COPY apps/sim/dist/worker.cjs
    Builder->>Runner: COPY packages → /app/packages (new line)

    Worker->>Runner: require('@sim/logger')
    Runner->>Runner: Node resolution: check node_modules/@sim/logger
    alt node_modules/@sim/logger exists
        Runner-->>Worker: ✅ resolves @sim/logger
    else node_modules/@sim/logger missing
        Runner-->>Worker: ❌ MODULE_NOT_FOUND — packages copy alone is not enough
    end

Loading

_{Reviews (1): Last reviewed commit: "update dockerfile" | Re-trigger Greptile}

[greptile-apps]

Only packages/logger is needed — avoid copying all packages

The worker only imports @sim/logger; every other processor file in apps/sim/worker/ also imports exclusively from @sim/logger (confirmed across all 9 files). Copying the entire packages tree brings in:

• packages/db — SQL migration files and Drizzle config that have no place in the production runner
• packages/testing — test utilities that should never be in a production image
• packages/cli and packages/ts-sdk — unrelated tooling

Consider limiting the copy to only what the worker actually requires:

Suggested change

	COPY --from=builder --chown=nextjs:nodejs /app/packages ./packages
	COPY --from=builder --chown=nextjs:nodejs /app/packages/logger ./packages/logger

This keeps the image lean and avoids shipping dev/test artifacts into production.

[greptile-apps]

Verify node_modules/@sim/logger symlink is present at runtime

worker.cjs is built with --packages=external, so it emits a bare require('@sim/logger') at runtime. For that require to resolve, Node/Bun must find @sim/logger somewhere in the node_modules lookup chain (e.g. /app/node_modules/@sim/logger).

With Bun's --linker=hoisted, that entry is typically a symlink pointing to ../../packages/logger. Copying packages/logger to /app/packages/logger in the runner satisfies the symlink target — but only if the symlink itself was preserved when the standalone output was copied via:

COPY --from=builder --chown=nextjs:nodejs /app/apps/sim/.next/standalone ./

Docker's COPY resolves symlinks and copies the target contents rather than preserving the symlink. If Next.js's standalone tracer also dereferenced the symlink (copying the real files), then the packages directory copy is redundant. If it did not (omitting @sim/logger from standalone entirely because only the non-Next.js worker uses it), then node_modules/@sim/logger may not exist at all in the runner, and copying packages/logger alone still won't create the missing node_modules entry.

A reliable, self-contained alternative is to bundle @sim/logger directly into worker.cjs by removing it from the externals scope, or by explicitly installing the workspace package into the runner's node_modules. Worth validating in the in-progress test that the worker actually starts and logs successfully.