fix: force Node.js 22 for Vercel deployment

[adryserage]

Summary

• Add .nvmrc file to force Vercel to use Node.js 22 instead of 24
• Fixes isolated-vm compilation failure due to C++20 requirement on Node.js 24

Problem

Vercel now defaults to Node.js 24.x, but the isolated-vm package fails to compile because:

1. No prebuilt binaries exist for Node.js 24
2. The C++ compiler on Vercel's build environment doesn't support C++20 (required by Node.js 24's V8 headers)

Error: #error "C++20 or later required."

Solution

Add .nvmrc with value 22 to ensure Vercel uses Node.js 22, which has prebuilt binaries for isolated-vm.

Test plan

• [ ] Verify Vercel deployment succeeds with Node.js 22
• [ ] Confirm isolated-vm installs without compilation

[vercel[bot]]

@adryserage is attempting to deploy a commit to the Typebot Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai[bot]]

[!IMPORTANT]

Review skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing touches

🧪 Generate unit tests (beta)

• [ ] Create PR with unit tests
• [ ] Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[vercel[bot]]

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

Project	Deployment	Preview	Comments	Updated (UTC)
builder-v2	Ready	Preview	Comment	Nov 26, 2025 10:12am

[baptisteArno]

In theory, having

"engines": {
    "node": "^22"
  },

in package.json should be enough 🤔

Maybe it should be added to apps/builder/package.json as well