Handle Unicode text, emoji, encoding, normalization, code points, and safe storage.
Lessons
Recognize and fix broken characters caused by mismatched encodings.
Debugging Encoding Problems is easiest to learn by reading the example, changing it, and observing the result.
// Encoding survival checklist:
// 1. Save every file as UTF-8 (without BOM)
// 2. <meta charset="UTF-8"> in the first line of <head>
// 3. Send Content-Type: ...; charset=utf-8
// 4. Use utf8mb4 in MySQL (not "utf8")
// 5. Count graphemes for emoji, not .length
// 6. normalize('NFC') before comparing user text
const visibleLength = str =>
[...new Intl.Segmenter().segment(str)].length;
console.log(visibleLength('👍🏽')); // 1Practice the Debugging Encoding Problems example in a small scratch file, then explain what changed and why.
In accordance with Section 6 & Section 7 of the DPDP Act 2023, third-party analytics and marketing trackers are strictly gated behind your affirmative consent. You may withdraw consent at any time under Section 6(4).
Essential for session authentication (ci_session), Cross-Site Request Forgery security (csrf_cookie_name), and Cloudflare DDoS/bot prevention. Cannot be disabled.
Gated under DPDP Section 7. Allows Google Analytics 4 (Google Consent Mode v2) to measure aggregate, anonymized tool usage.
Enables browser local storage to preserve your theme selection (dark/light mode) and code editor layout between visits.
Used to display developer sponsorships and native tool partner notices.