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

Updated: 2026年5月31日

Console Log

Original task (JA): コンソールに出力

📌

Conclusion

Console Log — free browser-based JavaScript practice

■ What this exercise teaches console.logで「Hello」と出力してください。

Why it matters in real projects

console.logはデバッグや確認用に値を出力します。 Similar patterns appear daily in code review and production UI work.

Step-by-step workflow

1. Read the guide and understand the goal of "Console Log" 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: Hello, hello, helo. 6. After success, continue with adjacent exercises in the same category

Core concept explained

console.logはデバッグや確認用に値を出力します。

Technical focus

Key JavaScript APIs: console.log.

Hint before you peek at the solution

console.log('Hello') と書きます。

Sample solution walkthrough

JavaScript APIs used: console.log. Verify spelling and async/await usage. Explanation: console.logはデバッグや確認用に値を出力します。 Hint recap: console.log('Hello') と書きます。

Solution code

📝 Sample code
console.log('Hello');

Common mistakes for this exact task

・Skipping the hint: console.log('Hello') と書きます。

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: Hello, hello, helo. 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 "Console Log" 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 ・Mention responsive or accessibility trade-offs ・Describe when you use: console.log

What to do after you pass

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

Keywords

Free hands-on exercise covering コンソールに出力, js-basic, 入門, console.log, console log—search-friendly guide for Console Log.

🧪 Try it here — safe to break things

Use the editor below to write code and preview instantly.

Jump to editor

■ Exercise task

console.logで「Hello」と出力してください。

Hint if stuck

console.log('Hello') と書きます。

10pt

コンソールに出力

console.logでHelloと出力してください。

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

Roadmap · All guides

Deep dive

"Console Log" is a 入門-level JavaScript exercise. console.logで「Hello」と出力してください。 Run it in-browser with automatic checking.

console.logはデバッグや確認用に値を出力します。 Similar patterns appear daily in code review and production UI work.

Pair this with the js-basic roadmap. Exercise #21 reinforces core js-basic skills.

Step-by-step workflow

  1. Read the guide and understand the goal of "Console Log"
  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: Hello, hello, helo.
  6. After success, continue with adjacent exercises in the same category

How to read the sample solution

JavaScript APIs used: console.log. Verify spelling and async/await usage. Explanation: console.logはデバッグや確認用に値を出力します。 Hint recap: console.log('Hello') と書きます。

Real-world & career relevance

JS basics precede React, Vue, and Node. Variables, functions, and arrays appear in daily code review.

Common mistakes

  • Skipping the hint: console.log('Hello') と書きます。
  • Typos in console.log
  • Loose == between string and number
  • Reassigning const
  • Missing semicolons causing odd line breaks

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: Hello, hello, helo. 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 "Console Log" 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
  • Mention responsive or accessibility trade-offs
  • Describe when you use: console.log

Glossary

const
Constant binding—no reassignment.
function
Reusable block of code.
console.log
Print to the developer console.

Keywords covered on this page

Free hands-on exercise covering コンソールに出力, js-basic, 入門, console.log, console log—search-friendly guide for Console Log.

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 "コンソールに出力"?

console.logはデバッグや確認用に値を出力します。 Hint: console.log('Hello') と書きます。

Where does js-basic fit?

JS basics precede React, Vue, and Node. Variables, functions, and arrays appear in daily code review.

Step-by-step for "Console Log"?

1. Read the guide and understand the goal of "Console Log"
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: Hello, hello, helo.
6. After success, continue with adjacent exercises in the same category

How to read the sample solution?

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

Explanation: console.logはデバッグや確認用に値を出力します。

Hint recap: console.log('Hello') と書きます。

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: Hello, hello, helo. 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 "Console Log" 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 Mention responsive or accessibility trade-offs Describe when you use: console.log

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?

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