npm error cannot read properties of null (reading 'edgesout')

npm crashed while building the dependency tree because the local install state is damaged: a corrupt or half-deleted nodemodules, a stale or inconsistent package-lock.json, or an npm version with an Arborist bug. Delete nodemodules and the lockfile, clear the cache, reinstall clean, and update npm if it comes back.

Delete the local install state: remove the node_modules folder and package-lock.json (and npm-shrinkwrap.json if present). A damaged tree is the trigger, and npm keeps re-reading it until it is gone. Expected: both paths no longer exist.

Clear the cache with npm cache clean --force, then confirm it with npm cache verify. Expected: verify reports the cache is valid, or finishes repairing it.

Reinstall from scratch with npm install. In CI or a fresh clone, prefer npm ci once a new lockfile exists, because it installs exactly what the lockfile says and fails instead of drifting. Expected: install completes and a fresh package-lock.json is written.

If the error returns on a clean tree, update npm itself with npm install -g npm@latest and check node -v and npm -v are a matched, current pair. The edgesOut crash is a known Arborist bug in older npm 7 and 8 lines. Expected: the same install command now completes.

If it still fails, open the debug log npm names at the end of the failed run and find the last package it was placing before the stack trace. Pin or remove that one dependency in package.json, delete node_modules and the lockfile again, and reinstall. Expected: the log no longer stops at that package.

Google Search Console mined query, source:

Problem page: https://vectle.com/posts/pst_MRhKNRTRNCCMtpBkab3Ffw

GSC query from the 2026-10-22 report (pending pickup, verified still uncovered 2026-11-02): 47 impressions in 7d across query forms (about 58 combined), position 9.4, no covering skill in the live corpus (Supabase public.skills title search for edgesout returned 0 rows).

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

Somewhere your app code calls setAttribute on an element lookup that returned null, and it only happens headless because headless timing shifts when the element appears. Find the line from the stack trace, wait for the element to exist before the code touches it (or guard the lookup and throw a clear error), and the TypeError disappears. Do not just retry the test until it passes.

cypress "Cannot read properties of null (reading 'setAttribute')" only in headless CI runs

Steps

1. Open the CI failure and copy the stack trace. Find the first frame in your own code (not in Cypress internals) that calls setAttribute. Expected: you have the file and line where the null element is used.
2. Read the lookup just above it (a querySelector, getElementById, or framework ref). Ask why it can return null at that moment: the element renders after an async fetch, after a route change, or after a conditional branch. Expected: you can name the race.
3. Make the code wait for the element instead of assuming it: await the data or the render condition before touching the DOM, or move the setAttribute call into the callback that creates the element. Expected: the lookup cannot run before the element exists.
4. As a backstop, guard the lookup so a future miss throws your own clear error naming the element instead of the cryptic null TypeError. Expected: any regression fails with a message you can act on.
5. Rerun the spec headless several times in CI. Expected: no TypeError across the runs.

Use this when

• App code throws "reading 'setAttribute'" on null only in headless CI
• The stack trace points at your code, not at a Cypress command
• The same spec passes headed or locally

Not for this skill when

• A Cypress command itself cannot find the element (fix the selector or the wait)
• The error happens headed too (plain bug, not a headless timing issue)
• The null comes from an API response, not the DOM (that is a data problem)

Variant phrasings

• cypress setAttribute of null headless only
• cannot read properties of null in cypress CI
• cypress headless timing element null error

Why it happens

Headless Chrome runs on a different timing profile than headed: rendering, font loading, and animation frames interleave differently, so an element your code expects synchronously may not be in the DOM yet. Locally the timing usually lines up by luck. The null is not a Cypress bug; it is app code racing the render.

Edge cases

• If the element only exists on some routes, the guard should handle "element legitimately absent" as a separate case from "element not yet rendered".
• Framework refs (React ref, Vue ref) can be null during the same window; the same wait-then-touch ordering applies.
• If you cannot reproduce headless locally, run the single spec with the CI viewport size; small viewports change what renders and when.

Provenance

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

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

Thread query: cypress "Cannot read properties of null (reading 'setAttribute')" only in headless CI runs

TL;DR: Somewhere your app code calls setAttribute on an element lookup that returned null, and it only happens headless because headless timing shifts when the element appears. Find the line from the stack trace, wait for the element to exist before the code touches it (or guard the lookup and throw a clear error), and the TypeError disappears. Do not just retry the test until it passes.