fix(trigger): mark cpu-features external to fix deploy build

[TheodoreSpeaks]

Summary

• Trigger.dev deploy build was failing: Could not resolve "../build/Release/cpufeatures.node" from cpu-features/lib/index.js.
• Root cause: ssh2 became reachable from the trigger background bundle via the Pi local SSH backend (feat(pi): add pi coding agent harness  #5178 wired executor/handlers/pi/ssh-tools.ts → app/api/tools/ssh/utils → ssh2). ssh2 was previously only used in API routes, which the trigger build never bundles.
• esbuild then tried to bundle ssh2's optional native dep cpu-features and choked on the missing compiled .node binary.
• Fix: add cpu-features to build.external in trigger.config.ts. ssh2 requires it inside a try/catch purely as a crypto-acceleration optimization, so externalizing it has no runtime impact.

Type of Change

• Bug fix

Testing

• Verified locally with trigger.dev deploy --dry-run --local-build → "Successfully built code" (build failed on the same step without the change).

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)

[cursor]

PR Summary

Low Risk
Single build-config external entry with no application logic changes; optional ssh2 dependency only.

Overview
Fixes Trigger.dev deploy failures when esbuild bundles the ./background graph after Pi SSH tooling pulled ssh2 into that bundle.

Adds cpu-features to build.external in trigger.config.ts alongside existing native/optional deps (isolated-vm, @earendil-works/pi-coding-agent). That stops the bundler from resolving ../build/Release/cpufeatures.node, which ssh2 only loads optionally inside a try/catch for crypto acceleration—so externalizing it should not change runtime behavior when the native module is absent.

^{Reviewed by Cursor Bugbot for commit e66afa6. Bugbot is set up for automated code reviews on this repo. Configure here.}

[greptile-apps]

Greptile Summary

Adds cpu-features to the esbuild build.external list in trigger.config.ts to fix a Trigger.dev deploy build failure caused by ssh2's optional native dependency becoming reachable through the background bundle.

• ssh2 was pulled into the trigger bundle after feat(pi): add pi coding agent harness  #5178 connected executor/handlers/pi/ssh-tools.ts → app/api/tools/ssh/utils → ssh2. esbuild then tried to resolve cpu-features (a compiled .node addon ssh2 conditionally requires for crypto acceleration) and failed. Externalizing cpu-features is safe because ssh2 loads it inside a try/catch as a pure optimization.
• cpu-features is deliberately not added to additionalPackages, so it won't be deployed to the Trigger.dev runtime — the graceful fallback path in ssh2 applies at runtime.

Confidence Score: 5/5

Safe to merge — the change is a minimal one-line addition to the esbuild external list that unblocks the Trigger.dev deploy build with no runtime behavior change.

The fix correctly targets only the native addon that esbuild cannot bundle. Since ssh2 wraps its require('cpu-features') call in a try/catch, externalizing the package does not remove any functionality — crypto acceleration simply falls back to the pure-JS path.

No files require special attention.

Important Files Changed

Filename	Overview
apps/sim/trigger.config.ts	Adds cpu-features to build.external to prevent esbuild from attempting to bundle the native .node binary pulled in transitively via ssh2; no other changes.

Sequence Diagram

%%{init: {'theme': 'neutral'}}%%
sequenceDiagram
participant TriggerBuild as Trigger.dev Build (esbuild)
participant BgBundle as Background Bundle
participant SSHTools as executor/handlers/pi/ssh-tools.ts
participant SSHUtils as app/api/tools/ssh/utils
participant ssh2 as ssh2 (npm)
participant cpufeatures as cpu-features (.node binary)
TriggerBuild->>BgBundle: bundle ./background
BgBundle->>SSHTools: import
SSHTools->>SSHUtils: import
SSHUtils->>ssh2: import
ssh2->>cpufeatures: "try { require('cpu-features') }"
alt Before fix
cpufeatures-->>TriggerBuild: Cannot resolve ../build/Release/cpufeatures.node
else After fix (cpu-features in build.external)
TriggerBuild->>TriggerBuild: skip cpu-features (external)
Note over cpufeatures: At runtime: require fails silently inside try/catch
end

Loading

%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
sequenceDiagram
participant TriggerBuild as Trigger.dev Build (esbuild)
participant BgBundle as Background Bundle
participant SSHTools as executor/handlers/pi/ssh-tools.ts
participant SSHUtils as app/api/tools/ssh/utils
participant ssh2 as ssh2 (npm)
participant cpufeatures as cpu-features (.node binary)
TriggerBuild->>BgBundle: bundle ./background
BgBundle->>SSHTools: import
SSHTools->>SSHUtils: import
SSHUtils->>ssh2: import
ssh2->>cpufeatures: "try { require('cpu-features') }"
alt Before fix
cpufeatures-->>TriggerBuild: Cannot resolve ../build/Release/cpufeatures.node
else After fix (cpu-features in build.external)
TriggerBuild->>TriggerBuild: skip cpu-features (external)
Note over cpufeatures: At runtime: require fails silently inside try/catch
end

Loading

_{Reviews (1): Last reviewed commit: "fix(trigger): mark cpu-features external..." | Re-trigger Greptile}