TypeError: x is not iterable
for…of, spread or destructuring was used on something that isn’t an array/iterable.
Exact message you may see
is not iterableobject is not iterableundefined is not iterable
Seen on:
JavaScript
Meaning
Plain objects, undefined and numbers aren’t iterable. Common when an API returns an object instead of an array, or data hasn’t loaded.
Common causes
- Spreading/looping undefined (data not loaded)
- Iterating a plain object instead of Object.entries()
- Destructuring a hook that returns an object as an array
- API shape changed
⚡ Quick fix
- Default to []: for (const x of items ?? [])
- Use Object.entries/keys/values for objects
- Log the value to confirm its type
Detailed fix by platform
JavaScript
for (const [key, value] of Object.entries(config)) { … }
How to diagnose
- Value — What is it actually?
- Source — API, props or state?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in JavaScript
- Failed to fetch TypeError: Failed to fetch / NetworkError when attempting to fetch resource
- QuotaExceededError QuotaExceededError: Failed to execute 'setItem' on 'Storage': Setting the value exceeded the quota
- module MIME type Failed to load module script: Expected a JavaScript module script but the server responded with a MIME type of "text/html"
Other ways to find it
Where this error sits
Origin: On your device. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Did this fix work for you?
Report a correction or suggest an improvement
Last updated 15 Oct 2026