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

Updated: 2026年5月31日

Template Literal

Original task (JA): テンプレートリテラル

📌

Conclusion

Template Literal — free browser-based JavaScript practice

■ What this exercise teaches name変数（「太郎」）を使って「こんにちは、太郎さん」とconsole.logで出力してください。

Why it matters in real projects

テンプレートリテラルで変数を文字列に埋め込めます。 Similar patterns appear daily in code review and production UI work.

Step-by-step workflow

1. Read the guide and understand the goal of "Template Literal" 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: こんにちは, 太郎. 6. After success, continue with adjacent exercises in the same category

Core concept explained

テンプレートリテラルで変数を文字列に埋め込めます。

Technical focus

Key JavaScript APIs: console.log.

Hint before you peek at the solution

バッククォートと${name}を使う

Sample solution walkthrough

JavaScript APIs used: console.log. Verify spelling and async/await usage. Explanation: テンプレートリテラルで変数を文字列に埋め込めます。 Hint recap: バッククォートと${name}を使う

Solution code

📝 Sample code
const name = '太郎';
console.log(`こんにちは、${name}さん`);

Common mistakes for this exact task

・Skipping the hint: バッククォートと${name}を使う

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: こんにちは, 太郎. 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 "Template Literal" 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, template literal—search-friendly guide for Template Literal.

🧪 Try it here — safe to break things

Use the editor below to write code and preview instantly.

Jump to editor

■ Exercise task

name変数（「太郎」）を使って「こんにちは、太郎さん」とconsole.logで出力してください。

Hint if stuck

バッククォートと${name}を使う

15pt

テンプレートリテラル

name変数（太郎）を使ってこんにちは、太郎さんとconsole.logで出力してください。

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

Roadmap · All guides

Deep dive

"Template Literal" is a 入門-level JavaScript exercise. name変数（「太郎」）を使って「こんにちは、太郎さん」とconsole.logで出力してください。 Run it in-browser with automatic checking.

テンプレートリテラルで変数を文字列に埋め込めます。 Similar patterns appear daily in code review and production UI work.

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

Step-by-step workflow

  1. Read the guide and understand the goal of "Template Literal"
  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: こんにちは, 太郎.
  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: テンプレートリテラルで変数を文字列に埋め込めます。 Hint recap: バッククォートと${name}を使う

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: バッククォートと${name}を使う
  • 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: こんにちは, 太郎. 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 "Template Literal" 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, template literal—search-friendly guide for Template Literal.

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 "テンプレートリテラル"?

テンプレートリテラルで変数を文字列に埋め込めます。 Hint: バッククォートと${name}を使う

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 "Template Literal"?

1. Read the guide and understand the goal of "Template Literal"
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: こんにちは, 太郎.
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: テンプレートリテラルで変数を文字列に埋め込めます。

Hint recap: バッククォートと${name}を使う

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: こんにちは, 太郎. 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 "Template Literal" 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?

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