💡 An editor is ready below the article—experiment freely!

Updated: 2026年5月31日

Api Error Handling

Original task (JA): エラーハンドリング

📌

Conclusion

Api Error Handling — free browser-based JavaScript practice

■ What this exercise teaches fetchで取得し、res.okがfalseなら「エラー」とconsole.log、trueならデータのtitleを出力してください。

Why it matters in real projects

res.okでHTTPステータスが成功かどうか判定します。 Similar patterns appear daily in code review and production UI work.

Step-by-step workflow

1. Read the guide and understand the goal of "Api Error Handling" 2. Review the JavaScript editor pane and start from the starter code 3. Open hints if stuck; compare your diff with the sample solution 4. Click Run and inspect preview/console output 5. Auto-check looks for output containing: sunt, aut, title. 6. After success, continue with adjacent exercises in the same category

Core concept explained

res.okでHTTPステータスが成功かどうか判定します。

Technical focus

Key CSS properties: https.

Hint before you peek at the solution

if (!res.ok) { ... } else { ... }

Sample solution walkthrough

JavaScript APIs used: console.log, fetch(, async , await . Verify spelling and async/await usage. Explanation: res.okでHTTPステータスが成功かどうか判定します。 Hint recap: if (!res.ok) { ... } else { ... }

Solution code

📝 Sample code
async function run() {
  const res = await fetch('https://jsonplaceholder.typicode.com/posts/1');
  if (!res.ok) {
    console.log('エラー');
  } else {
    const data = await res.json();
    console.log(data.title);
  }
}
run();

Common mistakes for this exact task

・Skipping the hint: if (!res.ok) { ... } else { ... } ・Forgetting await res.json() leaves you with a Promise object

Troubleshooting

Q: Preview does not change after Run A: Ensure you edited the JavaScript pane and clicked Run. Q: Looks correct but check fails A: Auto-check looks for output containing: sunt, aut, title. Look for typos, full-width spaces, or unclosed tags. Q: Console shows errors A: Open DevTools Console and fix bracket/quote mismatches at the reported line. Q: Hard to type on mobile A: Use landscape mode or continue on desktop—the same URL keeps progress in localStorage.

Interview / portfolio tips

・Explain the techniques in "Api Error Handling" in your own words within 30 seconds ・Practice walking through each line of the sample solution on a whiteboard ・Connect this task to a real component you would ship ・Discuss CSS properties: https ・Describe when you use: console.log, fetch(, async

What to do after you pass

Move to the next exercise in the api track, then continue the learning roadmap at /en/learning/api/.

Keywords

Free hands-on exercise covering エラーハンドリング, api, 中級, https, console.log, fetch(, async , await , api error handling—search-friendly guide for Api Error Handling.

🧪 Try it here — safe to break things

Use the editor below to write code and preview instantly.

Jump to editor

■ Exercise task

fetchで取得し、res.okがfalseなら「エラー」とconsole.log、trueならデータのtitleを出力してください。

Hint if stuck

if (!res.ok) { ... } else { ... }

25pt

エラーハンドリング

fetchで取得し、res.okがfalseならエラーとconsole.log、trueならデータのtitleを出力してください。

エラーをクリックで該当行をハイライト。✕=エラー ⚠=警告 ›=ログ。

Roadmap · All guides

Deep dive

"Api Error Handling" is a 中級-level JavaScript exercise. fetchで取得し、res.okがfalseなら「エラー」とconsole.log、trueならデータのtitleを出力してください。 Run it in-browser with automatic checking.

res.okでHTTPステータスが成功かどうか判定します。 Similar patterns appear daily in code review and production UI work.

Pair this with the api roadmap. Exercise #65 reinforces core api skills.

Step-by-step workflow

  1. Read the guide and understand the goal of "Api Error Handling"
  2. Review the JavaScript editor pane and start from the starter code
  3. Open hints if stuck; compare your diff with the sample solution
  4. Click Run and inspect preview/console output
  5. Auto-check looks for output containing: sunt, aut, title.
  6. After success, continue with adjacent exercises in the same category

How to read the sample solution

JavaScript APIs used: console.log, fetch(, async , await . Verify spelling and async/await usage. Explanation: res.okでHTTPステータスが成功かどうか判定します。 Hint recap: if (!res.ok) { ... } else { ... }

Real-world & career relevance

fetch + JSON appear in most real projects: weather apps, GitHub integrations, headless CMS.

Common mistakes

  • Skipping the hint: if (!res.ok) { ... } else { ... }
  • Forgetting await res.json() leaves you with a Promise object
  • Forgetting res.json() after fetch
  • Treating CORS as a code bug
  • No try-catch for network failures

Troubleshooting

Preview does not change after Run
Ensure you edited the JavaScript pane and clicked Run.
Looks correct but check fails
Auto-check looks for output containing: sunt, aut, title. Look for typos, full-width spaces, or unclosed tags.
Console shows errors
Open DevTools Console and fix bracket/quote mismatches at the reported line.
Hard to type on mobile
Use landscape mode or continue on desktop—the same URL keeps progress in localStorage.

Interview & portfolio tips

  • Explain the techniques in "Api Error Handling" in your own words within 30 seconds
  • Practice walking through each line of the sample solution on a whiteboard
  • Connect this task to a real component you would ship
  • Discuss CSS properties: https
  • Describe when you use: console.log, fetch(, async

Glossary

fetch
Browser API for HTTP requests.
JSON
Lightweight data interchange format.
CORS
Cross-origin browser security policy.

Keywords covered on this page

Free hands-on exercise covering エラーハンドリング, api, 中級, https, console.log, fetch(, async , await , api error handling—search-friendly guide for Api Error Handling.

Related dev tools

Learning roadmap

Learning roadmap →

Related exercises

Frequently asked questions

Is "エラーハンドリング" free?

This exercise is free and runs entirely in your browser. No account or credit card required.

Difficulty and time?

"エラーハンドリング" is level "中級". Read the guide first; beginners can usually finish within 30 minutes. Allow 5–15 minutes per exercise. Use hints, then the solution if stuck.

What after a correct answer?

After a correct answer, use "Next exercise". When you finish a category, continue on the learning roadmap.

Works on mobile?

Works on mobile browsers, but typing code is easier on a desktop.

Where are other exercises?

All exercises: /en/learn/ with category filters.

Key takeaway for "エラーハンドリング"?

res.okでHTTPステータスが成功かどうか判定します。 Hint: if (!res.ok) { ... } else { ... }

Where does api fit?

fetch + JSON appear in most real projects: weather apps, GitHub integrations, headless CMS.

Step-by-step for "Api Error Handling"?

1. Read the guide and understand the goal of "Api Error Handling"
2. Review the JavaScript editor pane and start from the starter code
3. Open hints if stuck; compare your diff with the sample solution
4. Click Run and inspect preview/console output
5. Auto-check looks for output containing: sunt, aut, title.
6. After success, continue with adjacent exercises in the same category

How to read the sample solution?

JavaScript APIs used: console.log, fetch(, async , await . Verify spelling and async/await usage.

Explanation: res.okでHTTPステータスが成功かどうか判定します。

Hint recap: if (!res.ok) { ... } else { ... }

Something is not working?

Preview does not change after Run → Ensure you edited the JavaScript pane and clicked Run.
Looks correct but check fails → Auto-check looks for output containing: sunt, aut, title. Look for typos, full-width spaces, or unclosed tags.
Console shows errors → Open DevTools Console and fix bracket/quote mismatches at the reported line.
Hard to type on mobile → Use landscape mode or continue on desktop—the same URL keeps progress in localStorage.

Career / interview angle?

Explain the techniques in "Api Error Handling" in your own words within 30 seconds Practice walking through each line of the sample solution on a whiteboard Connect this task to a real component you would ship Discuss CSS properties: https Describe when you use: console.log, fetch(, async

Can I change the starter code?

Yes—if it works. Understanding the starter first, then adding minimal diffs, speeds up learning.

What do the points mean?

25pt is a difficulty hint, not a score you must maximize.