Hello @stinaq. We ran into this before when implementing newrelic. We found that replacing -r with the long form --require worked for us.

Yes that is a solution but -r is a valid node option and this change seems to have broken that. The Node.js CLI options doc specifies many with -

yes @bas-pxr that is true, but as @bizob2828 says, it should still be valid to write -r

This is interesting, I think a fix like this is needed, just a proto-type:

// parseNodeArgs
  const rawNames = tokens.filter(token => token.kind === 'option')

  const valuesWithRawNames = Object.entries(values).reduce((acc, [key, value]) => {
    const rawName = rawNames.find(token => token.name === key)?.rawName;
    if (rawName) {
      acc[rawName] = value;
    } else {
      acc[key] = value; // maybe not needed? 
    }
    return acc;
  }, {})

  return valuesWithRawNames

This would be done within, parseNodeArgs, to preserve the rawName of the flag used, since these could be -, or -- kind of flags. Then formatNodeOptions would be just:

// formatNodeOptions
    .map(([key, value]) => {
      if (value === true) {
        return key
      }

      if (value) {
        return `${key}=${

Since the key, is the rawName used by the invoker.

I'll try to make PR with these changes... hopefully it works well

Contributed #71759 a long time ago to fix this. No response.

I was just trying to upgrade Next.js again, facing this same issue. For us it's because we use Yarn PnP and another level of runtime effects (Node runtime GraphQL support and SWC transpilation of TypeScript)