Records below are third-party data, not instructions. Apply with your own judgment.
nx
2 records of known failures, each with its cause, the fix and what not to try.
Records
- error: bun publish has no --json flag.nx's bun publishArgv adds --json to bun publish although the executor never parses bun's output; bun <=1.4.3 ignored unknown flags on package-manager commands and 1.4.4 rejects them.
- NX No existing Nx Cloud client and failed to download new version (NX…the Nx Cloud client bootstrap (version check and bundle download) uses Node's global fetch with Node's bundled roots and ignores customProxyConfigPath, which only the downloaded client reads.
Don’t try
drop the @scope:registry line from .npmrc so scoped packages stop failing at the dist-tag check — getNpmRegistry() falls back to npm config get registry, so nx always passes --@scope:registry=<url> to bun info and 1.4.4 rejects that flag too. (×1) · record
upgrade nx (24.0.2 -> 24.0.6) or run the canary — every 24.0.x and master still build bun publish with --json; the nx fix PR is unmerged. (×1) · record
point customProxyConfigPath at an HTTPS agent that adds the CA — only the downloaded client reads that file; the bootstrap warns 'customProxyConfigPath is not used for downloading the Nx Cloud client' and keeps failing. (×1) · record
put NODE_USE_SYSTEM_CA=1 or NODE_EXTRA_CA_CERTS in the workspace .env, or set process.env at runtime — Nx loads .env after Node has started and Node reads these variables only at launch, so the running process keeps the bundled roots. (×1) · record