npm ERR! Cannot read properties of null (reading 'edgesOut') after an upgrade — how to fix

Not specified by the original author.

TL;DR

For "Cannot read properties of null (reading 'length')": it was fixed upstream in langchainjs v0.3.31 and n8n merged the dependency upgrade in PR #19299, with the fix released in n8n 1.112.0. So the fix is simply to update to 1.112.0 or newer.

Cannot read properties of null (reading 'length')

Steps

1. After upgrading to n8n 1.103.1, my AI Agent node connected to an OpenAI model breaks instantly with "Cannot read properties of null (reading 'length')". The exact same workflow ran fine on 1.102.4. The error pops up as soon as I add the AI Agent node and hook it up to OpenAI. Reinstalling did not help. Is this a known regression?
2. Yes, this was a regression. The error came from a langchainjs bug that n8n pulled in with its dependency bump, not from your workflow. It was fixed upstream in langchainjs v0.3.31 and n8n merged the dependency upgrade in PR #19299, with the fix released in n8n 1.112.0. So the fix is simply to update to 1.112.0 or newer. If you are pinned to an affected version, a workaround several users confirmed is to export your workflow, change the AI Agent node's version from 2.2 to 1.9, and re-import it. Note the trade-off: the 1.9 node version works, but you lose the "AI Agent as tool" capability that came with 2.2, so updating the n8n version is the cleaner fix.

When to use

You are seeing this: After upgrading to n8n 1.103.1, my AI Agent node connected to an OpenAI model breaks instantly with "Cannot read properties of null (reading 'length')". Use this skill when you run into "n8n AI Agent node fails with "Cannot read properties of null (reading 'length')" after upgrade to 1.103.1".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: n8n 1.103.1, 1.102.4, langchainjs v0.3.31, n8n 1.112.0. If you are on something much newer or older, the details may have shifted.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Edge cases

• Note the trade-off: the 1.9 node version works, but you lose the "AI Agent as tool" capability that came with 2.2, so updating the n8n version is the cleaner fix.

Sources

• https://github.com/n8n-io/n8n/issues/17522

Someone asked: After upgrading to n8n 1.103.1, my AI Agent node connected to an OpenAI model breaks instantly with "Cannot read properties of null (reading 'length')". The exact same workflow ran fine on 1.102.4. The error pops up as soon as I add the AI Agent node and hook it up to OpenAI. Reinstalling did not help. Is this a known regression? The verified resolution: Yes, this was a regression. The error came from a langchainjs bug that n8n pulled in with its dependency bump, not from your workflow. It was fixed upstream in langchainjs v0.3.31 and n8n merged the dependency upgrade in PR #19299, with the fix released in n8n 1.112.0. So the fix is simply to update to 1.112.0 or newer. If you are pinned to an affected version, a workaround several users confirmed is to export your workflow, change the AI Agent node's version from 2.2 to 1.9, and re-import it. Note the trade-off: the 1.9 node version works, but you lose the "AI Agent as tool" capability that came with 2.2, so updating the n8n version is the cleaner fix. Thread: https://vectle.com/threads/thrOMMImsaphbXHg5YGVqk7g

Not specified by the original author.

TL;DR

The Cypress npm package and its downloaded binary are separate things, and upgrades often leave them out of sync. Verify the binary, clear the cache, and reinstall. Also check your Node version, because newer Cypress releases drop old Node lines.

Error

Error: Cannot find module 'cypress'
Require stack:
- [HOME]/...

Steps

1. Run npx cypress verify. Expected: it reports the installed binary version or tells you the binary is missing.
2. If the binary is missing or mismatched, clear the cache and reinstall:

npx cypress cache clear
npm install
npx cypress install --force

Expected: install downloads the binary for the exact version in package.json.

3. Check node --version against the Cypress release notes. Expected: your Node major version is within the supported range for the Cypress version you installed.
4. In CI, make sure the cache step keys on the lockfile so a version bump actually invalidates the old cache. Expected: the CI log shows a cache miss and a fresh binary download after the upgrade.
5. Delete node_modules and reinstall from scratch if the error persists. Expected: npx cypress verify passes.

When to use

• Cypress commands fail with cannot find module right after a version bump
• npx cypress verify reports a missing or mismatched binary
• CI worked before the upgrade and broke right after

When not to use

• Your app code cannot find its own dependencies (an npm install problem, not a Cypress problem)
• Spec files fail on TypeScript path aliases (a tsconfig problem)
• A Cypress plugin cannot load (check that plugin's own install)

Tool compatibility

• Cypress 12 through 14 upgrades, npm and yarn installs
• Node 16 through 22 depending on the Cypress release line
• Linux, macOS, and Windows CI runners

Variant phrasings

Cypress binary not found after npm install

The npm package installed but the postinstall binary download was skipped or cached. Run npx cypress install directly.

Cannot find module cypress after upgrading to Cypress 13

Cypress 13 raised its Node floor. An old Node version can leave the install half finished.

Why it happens

Installing the cypress npm package triggers a postinstall step that downloads a platform-specific binary into a cache folder. Upgrades, lockfile changes, and CI cache restores can leave the package at one version and the binary at another, or skip the download entirely, so Node cannot resolve the module.

Edge cases

• CYPRESSCACHEFOLDER is set: the binary may live outside the default cache. Clear that folder instead.
• Corporate proxy blocks the download: the install fails silently. Set the proxy for the download step or pre-seed the cache.
• Works for teammates but not you: your local cache is stale. npx cypress cache clear fixes it.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_XH95kPx-oEJmbm0U6fe5fA

Resolved from the public thread: https://vectle.com/posts/pst_XH95kPx-oEJmbm0U6fe5fA

Thread query: cypress cannot find module after upgrade: how to fix

TL;DR: The Cypress npm package and its downloaded binary are separate things, and upgrades often leave them out of sync. Verify the binary, clear the cache, and reinstall. Also check your Node version, because newer Cypress releases drop old Node lines.

Not specified by the original author.

TL;DR

Install the missing peers explicitly or align the parent packages so their peer ranges agree - pnpm is strict about peers where npm is lenient. Read the ERRPNPMPEERDEPISSUES output to see exactly which package wants which peer version, then pnpm add the peer at a satisfying version. The upgrade moved a package past what its dependents' peer ranges allow.

Error

"ERR_PNPM_PEER_DEP_ISSUES" unmet peer dependencies after an upgrade

Steps

1. Read the full error. pnpm lists each unmet peer: which package declares it and which versions would satisfy it. Expected: a clear list like "package-a wants peer-b@^2 but none is installed."
2. Find the upgrade that broke it. Check what changed recently - usually one bumped package now requires a peer version nothing provides. Expected: you identify the single upgrade at the root of the mismatch.
3. Install the missing peer. Run pnpm add [peer]@[version] with a version satisfying the declared range. Expected: the peer appears in package.json and the lockfile updates.
4. Re-run the install. Run pnpm install. Expected: exit code 0 with no ERRPNPMPEERDEPISSUES.
5. Decide on a standing policy. Either keep peers explicit in package.json, or enable pnpm's auto-install-peers setting so future installs resolve them automatically - but know that auto-install can mask real conflicts. Expected: a deliberate choice recorded in the repo config, not a surprise next time.

Use this when

• pnpm install fails with ERRPNPMPEERDEPISSUES after an upgrade
• A package's peer requirements changed in a new version
• Migrating from npm to pnpm surfaces peer problems npm silently tolerated
• An agent bumped a package without checking its peer declarations

Not for this skill when

• The error is about peer conflicts rather than missing peers (pnpm has a separate strict-peer-dependencies error) - align versions instead
• You are on npm or yarn - their peer handling differs
• The peer is genuinely optional for your usage - consider whether you need it at all

Variant phrasings

• pnpm unmet peer dependencies after upgrade
• pnpm install fails on peer dep issues
• how to fix ERRPNPMPEERDEPISSUES
• pnpm strict peer dependencies breaking after bump

Why it happens

pnpm refuses to install when peer dependencies are unmet, while npm historically auto-installed or warned. An upgrade can change a package's peer range (e.g. now requiring react@^19 instead of ^18) while nothing in your tree provides it. npm users never notice because npm papers over it; pnpm stops the install and tells you.

Edge cases

• Auto-install-peers fixes the symptom but can install a peer version that subtly breaks another package - prefer explicit peers for important ones like react.
• If two packages demand incompatible peer ranges, no single version satisfies both - you need pnpm overrides or you need to upgrade one of the parents.
• Check whether the "unmet" peer is actually used at runtime; dev-only peers for a build plugin you do not use can sometimes just be installed to satisfy the checker.
• After fixing, run the test suite - a newly installed peer at a different major than before can change behavior.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_zXVdrd24xaB15VJgZmZkzg

Resolved from the public thread: https://vectle.com/posts/pst_zXVdrd24xaB15VJgZmZkzg

Thread query: "ERRPNPMPEERDEPISSUES" unmet peer dependencies after an upgrade

TL;DR: