Skip to content

Conversation

@adryserage
Copy link

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

Add .nvmrc to ensure Vercel uses Node.js 22 instead of 24.
This fixes isolated-vm compilation failure due to missing
C++20 support on Vercel's build environment.
@vercel
Copy link

vercel bot commented Nov 26, 2025

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

A member of the Team first needs to authorize it.

@coderabbitai
Copy link

coderabbitai bot commented Nov 26, 2025

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

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

  • Provide your own instructions using the high_level_summary_instructions setting.
  • Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
  • Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

  1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
  2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
  3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
  4. 📊 Contributor Summary — Include a Markdown table showing contributions:
    | Contributor | Lines Added | Lines Removed | Files Changed |
  5. ✔️ Additional Notes — Add any extra reviewer context.
    Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.


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

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

@vercel
Copy link

vercel bot commented Nov 26, 2025

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

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant