I'm getting a weird (ERRCODE 243) error when installing a 3rd party js package using Rush.js by running `rush add --package <package>`

Question

my team is migrating to rush and I had a problem while setting it up: I'm getting a weird error when trying to add any 3rd party lib (let's say react) to package.json using rush add --package react (for example). The error log:

Found configuration in /home/ivan/dev/JS/eisbuk/rush.json

Rush Multi-Project Build Tool 5.66.2 - https://rushjs.io
Node.js version is 14.19.0 (LTS)

Found configuration in /home/ivan/dev/JS/eisbuk/rush.json

Starting "rush add"

Determining new version for dependency: react
No version selector was specified, so the version will be determined automatically.

Trying to acquire lock for pnpm-6.32.3
Acquired lock for pnpm-6.32.3
Found pnpm version 6.32.3 in /home/ivan/.rush/node-v14.19.0/pnpm-6.32.3

Symlinking "/home/ivan/dev/JS/eisbuk/common/temp/pnpm-local" --> "/home/ivan/.rush/node-v14.19.0/pnpm-6.32.3"
The "ensureConsistentVersions" policy is NOT active, so we will assign the latest version.

Querying NPM registry for latest version of "react"...

ERROR: The command failed with exit code 243

I tried to find a similar problem report related to rush and looked up the 243 error with npm, both to no avail. I'm using pnpm, however, the error persists with npm and yarn all the same (with yarn it's exit code 1, everything else is the same).

Here's my .npmrc (a default really):

registry=https://registry.npmjs.org/
always-auth=false

Interestingly enough, if I manually add a dependency to package.json and run rush update, the update goes well and the dep is added to node_modules and shrinkwrap (so it shouldn't be an npm registry problem). Here's my rush.json:

{
  "$schema": "https://developer.microsoft.com/json-schemas/rush/v5/rush.schema.json",
  "rushVersion": "5.66.2",
  "pnpmVersion": "6.32.3",
  "pnpmOptions": {
    "preventManualShrinkwrapChanges": true,
    "useWorkspaces": true
  },
  "nodeSupportedVersionRange": ">=12.13.0 <13.0.0 || >=14.15.0 <15.0.0 || >=16.13.0 <17.0.0",
  "gitPolicy": {},
  "repository": {},
  "eventHooks": {
    "preRushInstall": [],
    "postRushInstall": [],
    "preRushBuild": [],
    "postRushBuild": []
  },
  "variants": [],
  "projects": [
    /** ...other projects */
    {
      "packageName": "@eisbuk/functions",
      "projectFolder": "packages/functions"
    }
    /** ...other projects */
  ]
}

The entire repo can be found at: https://github.com/eisbuk/EisBuk/tree/feature/rush

Answer 1

Solved!

In the end, I've managed to pinpoint it to the node version. I was using v14.19.0 and bumping to v16.14.2 solved it. I don't know if it's a known incompatibility, but here it is.