0Pricing
Vibe Coding · 课时

理解错误信息

在将错误粘贴给人工智能之前，先阅读并理解错误信息。

理解错误信息 是 CoddyKit 上的免费 Vibe Coding 课时。 这是第 1 节课，共 4 节。 你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。 这是 Vibe Coding 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 Vibe Coding 课程共包含 4 节课。

本课时的部分内容尚未翻译，以英文显示。

Errors Are Clues, Not Walls

When you're building with AI and something breaks, your screen fills up with red text. It feels scary. But here's the truth: an error message is a clue, not a wall.

The computer is literally telling you what went wrong and where. Once you learn to read these clues, debugging becomes a conversation instead of a panic. And when you pair that skill with AI, you'll fix bugs faster than most experienced developers.

In this lesson, you'll learn to read errors before you paste them to tools like Cursor, Claude Code, or Copilot.

Anatomy of an Error

Most error messages have three parts you should hunt for:

  • The type — what kind of problem (e.g. TypeError, ReferenceError)
  • The message — a short human-ish description
  • The location — file name and line number

Here is a classic JavaScript error. Read it slowly, left to right.

TypeError: Cannot read properties of undefined (reading 'name')
    at showUser (app.js:14:22)
    at main (app.js:30:3)

Decode That Error

Let's decode the error from the last scene piece by piece:

  • TypeError → the kind of bug: we used a value the wrong way
  • Cannot read properties of undefined (reading 'name') → we tried to grab .name off something that doesn't exist
  • at showUser (app.js:14:22) → it happened in the showUser function, file app.js, line 14, column 22

That last part is gold. You now know exactly where to look: line 14.

The Stack Trace

The list of at ... lines is called the stack trace. Read it top to bottom: the top line is where the error actually exploded, and each line below shows what called it.

Beginners often paste the whole thing to AI and ignore it. But just glancing at the top line tells you which function to inspect first. The lines mentioning your own files matter most — lines deep in libraries are usually not your bug.

at showUser (app.js:14:22)   ← your code, START HERE
at main (app.js:30:3)        ← your code, who called it
at node_modules/.../run.js   ← library, usually ignore

See an Error Happen Live

Let's actually trigger one. Run this snippet. It tries to read .toUpperCase() on a value that is undefined, which throws the same family of error.

Read the message it prints — notice how it names the exact problem.

const user = { email: "ada@example.com" };
try {
  console.log(user.name.toUpperCase());
} catch (err) {
  console.log("Error type:", err.name);
  console.log("Message:", err.message);
}

Common Error Types

You'll meet the same handful of errors over and over. Knowing them on sight saves time:

  • SyntaxError — a typo the computer can't even read (missing bracket, comma)
  • ReferenceError — you used a name that doesn't exist (typo'd variable)
  • TypeError — a value exists but you used it the wrong way
  • RangeError — a number or length is out of bounds

When you can name the error type, you can tell AI what category of fix you need.

Read Before You Paste

Here's the habit that separates fast builders from frustrated ones: read the error for 10 seconds before reaching for AI.

Ask yourself three quick questions:

  • What's the error type?
  • What file and line does it point to?
  • What was I just doing when it broke?

Even if you still hand it to AI, answering these makes your prompt far sharper — and you'll often spot the fix yourself before AI even replies.

Errors Point at the Symptom, Not Always the Cause

One subtle trap: the line in the error is where things blew up, but the real cause might be earlier. In our example, line 14 reads user.name — but the actual bug might be that user was loaded wrong on line 8.

So treat the error location as your starting point, then trace backwards: where did this value come from? AI is great at this once you point it to the right region.

Browser vs Terminal Errors

You'll see errors in two main places:

  • Browser Console (press F12, click Console) — for front-end web code. Click the file:line link and it jumps you right to the code.
  • Terminal — for back-end / Node.js / build tools. Same anatomy, just no clickable link.

Tools like Replit, Bolt, and Cursor often surface these inline and even add a 'Fix with AI' button. But that button works best when you already understand the message.

A Quick Reading Drill

Read this error and try to answer in your head before scrolling: What type? What line? What's missing?

Answer: It's a ReferenceError — the variable totl doesn't exist (a typo for total) — on line 7. The fix is a one-character spelling correction. No AI needed, just careful reading.

ReferenceError: totl is not defined
    at calculateCart (cart.js:7:18)

Turn Reading Into a Reflex

Run this final example. It deliberately misspells a variable. Watch the console name the exact problem — then imagine how fast you'd fix it knowing how to read it.

The goal isn't to memorize every error. It's to build the reflex: stop, read the type, read the line, then act.

const total = 42;
try {
  console.log(totl); // typo on purpose
} catch (err) {
  console.log(err.name + ": " + err.message);
}

Quick Check

You see: TypeError: Cannot read properties of undefined (reading 'name') at showUser (app.js:14:22). Where should you look FIRST?

Recap: You Can Read Errors Now

You leveled up from 'red text = panic' to 'red text = clue'. You learned to:

  • Spot the error type, message, and location
  • Read a stack trace top-down and focus on your own files
  • Recognize common types: Syntax, Reference, Type, Range
  • Treat the error line as a starting point, then trace backwards

Next up: how to take this understanding and paste errors to AI effectively so it fixes the bug on the first try.

常见问题解答

「理解错误信息」课时是免费的吗？

是的 — 「理解错误信息」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 Vibe Coding 课程的其余内容，请升级到 CoddyKit PRO。 Vibe Coding 课程共包含 4 节课。

「理解错误信息」这节课中我会学到什么？

在将错误粘贴给人工智能之前，先阅读并理解错误信息。 你通过在浏览器中直接运行的动手代码来练习 Vibe Coding，全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 Vibe Coding 需要有经验吗？

无需任何先前经验。CoddyKit 上的 Vibe Coding 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。 这是第 1 节课，共 4 节。

「理解错误信息」课时需要多长时间？

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。

我能在这节 Vibe Coding 课中编写并运行代码吗？

能。每节 Vibe Coding 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

  1. 理解错误信息
  2. 有效地将错误粘贴给人工智能
  3. 缩小错误范围
  4. 人工智能卡住时怎么办
← 返回 Vibe Coding