Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -189,7 +189,7 @@ Written up where the work happens, not in a style guide:

## Quick start

You need [Bun](https://bun.com) and Docker.
You need [Bun](https://bun.com), [Node.js](https://nodejs.org) 24 or newer, and Docker. Bun runs the API and the scripts; Next.js and the eve agent run on Node.

```sh
git clone https://github.com/trycompai/crm.git && cd crm
Expand Down
2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@
"typescript": "5.9.2"
},
"engines": {
"node": ">=22"
"node": ">=24"

@cubic-dev-ai cubic-dev-ai Bot Sep 5, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P3: The PR describes the engines bump as documentation-only because Bun does not enforce engines, but this repo is deployed on Vercel, and Vercel reads engines.node from the root package.json to select the Node.js build and serverless runtime version. So this change does alter the production Node runtime to 24, not just the number a self-hoster reads. That is likely intended (eve requires Node 24), but the stated rationale is inaccurate, so verify the Vercel build/runtime behaves as expected rather than assuming there is no build impact.

Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At package.json, line 35:

<comment>The PR describes the engines bump as documentation-only because Bun does not enforce `engines`, but this repo is deployed on Vercel, and Vercel reads `engines.node` from the root package.json to select the Node.js build and serverless runtime version. So this change does alter the production Node runtime to 24, not just the number a self-hoster reads. That is likely intended (eve requires Node 24), but the stated rationale is inaccurate, so verify the Vercel build/runtime behaves as expected rather than assuming there is no build impact.</comment>

<file context>
@@ -32,7 +32,7 @@
 	},
 	"engines": {
-		"node": ">=22"
+		"node": ">=24"
 	},
 	"packageManager": "bun@1.3.12",
</file context>
Fix with cubic

},
"packageManager": "bun@1.3.12",
"devEngines": {
Expand Down