-
Notifications
You must be signed in to change notification settings - Fork 30.7k
Labels
Script (next/script)Related to Next.js Script Optimization.Related to Next.js Script Optimization.
Description
Link to the code that reproduces this issue
https://github.com/stinaq/newrelic-node-examples/tree/main/nextjs/nextjs-app-router
To Reproduce
npm installto get correct dependenciesnpm run devto start dev server
running this runs the command
NODE_OPTIONS='-r dotenv/config --loader newrelic/esm-loader.mjs -r newrelic' next devit's starting the dev server according to Newrelic setup.
I filed an issue over at their repo, but they are saying the issue comes from the next CLI.
Current vs. Expected behavior
When running this command, starting the server fails with the following error message:
--r= is not allowed in NODE_OPTIONS
note that the command run does not include --r.
Expected behavior is that the server can run
Provide environment information
Operating System:
Platform: darwin
Arch: arm64
Version: Darwin Kernel Version 24.3.0: Thu Jan 2 20:24:24 PST 2025; root:xnu-11215.81.4~3/RELEASE_ARM64_T6030
Available memory (MB): 18432
Available CPU cores: 12
Binaries:
Node: 20.19.0
npm: 10.8.2
Yarn: N/A
pnpm: 9.5.0
Relevant Packages:
next: 15.2.4 // Latest available version is detected (15.2.4).
eslint-config-next: 14.1.4
react: 19.0.0
react-dom: 19.0.0
typescript: 5.8.2
Next.js Config:
output: N/AWhich area(s) are affected? (Select all that apply)
Script (next/script)
Which stage(s) are affected? (Select all that apply)
next dev (local)
Additional context
I filed an issue over at their repo, but they are saying the issue comes from the next CLI.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Script (next/script)Related to Next.js Script Optimization.Related to Next.js Script Optimization.