🎓 Free Capstone Projects with Full Documentation, ER Diagrams & Source Code — Updated Weekly for 2026
👨‍💻 Free Source Code & Capstone Projects for Developers

Python & JavaScript TypeError Reference — 220+ Fixed Errors with Solutions (2026)

itsourcecode.com hosts 220+ documented fixes for Python and JavaScript TypeErrors: the most common runtime error class for both languages. Whether you hit TypeError: 'NoneType' object is not subscriptable in Python or Uncaught TypeError: Cannot read property 'map' of undefined in Node.js, you’ll find the exact error with a step-by-step fix below. Each post explains why the error happens, shows a minimal reproduction, and gives 2–4 ways to fix it. Browse by error family or search the archive for your specific error message.

What is a TypeError?

A TypeError is raised when an operation or function is applied to a value of the wrong type. In Python, the interpreter raises TypeError with a message like “unsupported operand type(s) for +: ‘int’ and ‘str'”. In JavaScript, the runtime throws TypeError with messages like “Cannot read property X of undefined” or “X is not a function”. TypeErrors are the most common runtime exception in both languages because both are dynamically typed — variables don’t declare their type, so type mismatches only surface at execution.

How to debug any TypeError in 4 steps

  1. Read the full message — it usually names both types involved (e.g., “int and str”, “NoneType and dict”). The mismatch is your clue.
  2. Find the exact line — Python tracebacks point to the line; JavaScript stack traces point to the file and line. Look at the variable on that line.
  3. Print the type — add print(type(variable)) in Python or console.log(typeof variable, variable) in JavaScript before the failing line. This tells you what type the variable actually is at runtime.
  4. Trace where the type went wrong — if your variable is None or undefined when you expected a list/object, walk backwards through the code until you find where it got the wrong value (usually a function returning None instead of a list, or an async response that hasn’t resolved).

Featured TypeErrors by error family

The 220+ errors in this archive group into a few common families. Jump to your family below.

🟦 JavaScript: “Cannot read property X of undefined / null”

The most common JavaScript TypeError. You’re trying to access a property on a value that’s undefined or null — usually an unawaited promise, a missing object field, or a state variable that hasn’t been initialized yet.

🟦 JavaScript: “X is not a function”

You’re calling something that exists but isn’t a function — usually because you imported the wrong thing, a library API changed between versions, or you destructured an object incorrectly.

🟦 JavaScript: “X is not a constructor”

You’re calling new X() on something that isn’t a constructor function — usually a default vs named import mistake or an old library version.

🟢 Python: “‘X’ object is not callable”

You’re treating a non-function as a function (calling it with parentheses). Common causes: shadowing a built-in name (list, str, dict) with a variable, or accidentally using = instead of ==.

🟢 Python: “‘X’ object is not subscriptable”

You’re using square-bracket indexing (x[0]) on a value that doesn’t support indexing. Most commonly happens with None, methods, or values that look like collections but aren’t.

🟢 Python: NoneType errors (14 distinct messages)

A function returned None when you expected a value. Almost always caused by forgetting to return something, an unsuccessful API call, or chaining operations on a function that doesn’t return.

🟢 Python: “Object of type X is not JSON serializable”

You’re calling json.dumps() on a value that JSON doesn’t know how to encode — usually a NumPy/Pandas type, a datetime, or a custom class. Fix by converting first or providing a custom encoder.

🟢 Python: “unsupported operand type(s) for X”

You used an operator (+, -, *, etc.) between two values whose types don’t combine that way. Most common: adding str + int, or anything involving None.

🟢 Python: “missing N required positional argument(s)”

You called a function or method without providing all required arguments. Common when calling methods on classes you forgot to instantiate (e.g., MyClass.method() instead of MyClass().method()).

2026 Updated Guides — featured TypeError fixes

These guides were rewritten or expanded in May 2026 with current library versions, minimal reproductions, and 3–4 alternative fixes each. Start here if your error is in the list.

TypeErrors by library / framework

Library-specific TypeErrors that appear repeatedly in the archive — bookmark this section if you work in any of these stacks.

  • pandas: Object of type DataFrame is not JSON serializable · The truth value of a Series is ambiguous · unhashable type: ‘Series’ · Column is not iterable · ‘AxesSubplot’ object is not subscriptable
  • NumPy: Object of type float32 is not JSON serializable · unsupported format string passed to numpy.ndarray.__format__ · numpy.float64 object is not callable
  • scikit-learn: fit() missing 1 required positional argument: y
  • matplotlib: ‘AxesSubplot’ object is not subscriptable
  • Three.js: THREE.OrbitControls is not a constructor
  • Express.js: res.status is not a function
  • Node.js: fsevents.watch is not a function · loaderContext.getOptions is not a function · Cannot read property ‘map’ of undefined
  • asyncio / async: NoneType can’t be used in ‘await’ expression
  • multiprocessing: cannot pickle ‘_thread.lock’ object · cannot pickle ‘_thread.RLock’ object

Related error categories

TypeError is one of 10 hubs in our Python & JavaScript error reference cluster — 980+ documented fixes total. If your error isn’t a TypeError, jump to the right hub below:

About this TypeError reference

This TypeError reference has been built since 2015 by PIES Information Technology Solutions in Binalbagan, Negros Occidental, Philippines. Each post in the collection comes from a real error encountered in production code — by us, by our clients, or by readers who emailed us with their tracebacks. Used by 12,000+ developers and students monthly across the Philippines, India, the United States, and beyond. If your TypeError isn’t here, send the full error message and traceback to our contact form and we’ll add it.

Frequently Asked Questions

What is the difference between TypeError and ValueError in Python?
A TypeError means the value's type is wrong for the operation (e.g., trying to add a string to an integer). A ValueError means the value's type is correct but its content is invalid (e.g., calling int("abc") — string is the right type, but "abc" is not a valid integer). If the error message names two types, it is TypeError. If it says the value is invalid for a specific function, it is ValueError.
Why do TypeErrors happen more in Python and JavaScript than in Java or C++?
Because Python and JavaScript are dynamically typed — variables do not declare their type, so type mismatches only surface at runtime. Java and C++ are statically typed, so the compiler catches type mismatches before the program runs. The tradeoff is faster development cycles in Python/JS but more runtime debugging. Type hints (Python 3.5+) and TypeScript reduce this gap significantly.
Should I catch TypeErrors with try/except or try/catch?
Generally no. A TypeError almost always indicates a bug in your code, not a recoverable condition. Catching and ignoring TypeErrors hides bugs. The exception: when you are parsing untrusted external input (user-uploaded JSON, third-party API responses), wrapping the parse step in try/except is reasonable — but log the error so you know it happened.
How do I prevent TypeErrors in Python?
Three practices that prevent about 80% of TypeErrors: (1) Use type hints on function parameters and return values — def parse(text: str) -> list[int]:. (2) Run mypy or pyright in CI to catch type errors before deploy. (3) Check for None explicitly when a function might return it (if result is None: return). The first two are static; the third is runtime.
How do I prevent TypeErrors in JavaScript?
Use TypeScript. It compiles to JavaScript but adds compile-time type checking that catches most TypeErrors before deploy. If TypeScript is not an option, use optional chaining (obj?.prop?.method?.()) to safely access properties that might be undefined, and nullish coalescing (value ?? defaultValue) to provide defaults.
What does "Cannot read property X of undefined" actually mean?
It means you tried to do variable.X where variable is undefined (the value JavaScript assigns when something does not exist). Most commonly: an API response field is missing, a React state has not initialized yet, an async function has not resolved, or you destructured an object that turned out to be undefined. Always check the variable IS defined before accessing properties.
Are these fixes safe to use in production code?
The fixes documented here are battle-tested patterns commonly used in production. However, you should still understand why the error happened in your specific context before applying a fix — the same error message can have different root causes in different codebases. The debug-in-4-steps process above helps you confirm the diagnosis before patching.
How often is this TypeError reference updated?
New TypeError posts are added weekly as we encounter them in real codebases. Existing posts are revised every 6-12 months to keep up with library version changes (e.g., Express 5, pandas 2.x, NumPy 2.0, Three.js r160+). This page was last refreshed in May 2026.

Itsourcecode.com is your trusted resource for free source code, capstone projects with full documentation, and step-by-step programming tutorials.

Built by PIES IT Solutions

Binalbagan, Negros Occidental, Philippines

Quick Links

Top Categories

Get Free Capstone Resources

Subscribe for weekly updates and free resources delivered to your inbox.

© 2026 Itsourcecode.com | All rights reserved|
Built with ❤️ by PIES Information Technology Solutions