Fix Next.js 15.4+ build failure with NODE_OPTIONS -r flag

[Copilot]

Next.js 15.4.0+ incorrectly transforms -r to --r= in NODE_OPTIONS, causing build failures with Node.js v24 and monitoring tools (Dynatrace, NewRelic) that inject the short-form flag.

Changes

• Downgrade Next.js: Pin to 15.3.5 (last stable version before regression)
• Add troubleshooting docs: Document error, root cause, and workarounds (unset NODE_OPTIONS, use --require long-form, disable monitoring injection, use Node v20)

Context

Error occurs during build:

$ npm run build
--r= is not allowed in NODE_OPTIONS
Next.js build worker exited with code: 9

Upstream issue: vercel/next.js#77550

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• scarf.sh
  • Triggering command: node ./report.js (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>--r= is not allowed in NODE_OPTIONS</issue_title>
<issue_description>After updating the falkordb-browser today, I cannot build it anymore:

[@ falkordb-browser]$ npm run build --verbose
npm verbose cli .../v24.10.0/bin/node .../v24.10.0/bin/npm
npm info using [email protected]
npm info using [email protected]
npm verbose title npm run build
npm verbose argv "run" "build" "--loglevel" "verbose"
npm verbose logfile logs-max:10 dir:~/.npm/_logs/2025-10-27T12_51_22_245Z-
npm verbose logfile ~/.npm/_logs/2025-10-27T12_51_22_245Z-debug-0.log

> [email protected] build
> next build

   ▲ Next.js 15.5.2
   - Environments: .env

   Creating an optimized production build ...
 ✓ Compiled successfully in 8.4s
   Linting and checking validity of types  .../v24.10.0/bin/node: --r= is not allowed in NODE_OPTIONS
Next.js build worker exited with code: 9 and signal: null
npm verbose cwd ~/Dev/falkordb-browser
npm verbose os Linux 5.14.0-570.52.1.el9_6.x86_64
npm verbose node v24.10.0
npm verbose npm  v11.6.1
npm verbose exit 9
npm verbose code 9

Steps to reproduce:
git checkout tags/v1.4.9
npm i
npm run build

What I've done, suggested by problems found in the internet:
rm -rf .next
rm -rf ~/.npm
Nothing changes.</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes --r= is not allowed in NODE_OPTIONS #1203

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[vercel]

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

Project	Deployment	Preview	Comments	Updated (UTC)
falkordb-browser	Ready	Preview	Comment	Nov 2, 2025 8:59am

[coderabbitai]

Important

Review skipped

Bot user detected.

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.

---

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