Membangun Pengalih Mode Gelap
Implementasikan pengalih JavaScript yang menambahkan dan menghapus kelas dark pada elemen html serta menyimpan preferensi di localStorage.
Membangun Pengalih Mode Gelap adalah pelajaran Tailwind CSS Academy gratis di CoddyKit. Ini adalah pelajaran 3 dari 4. Kamu bisa membaca pelajaran lengkapnya di bawah secara gratis — lalu praktikkan langsung di browser dengan editor kode bawaan dan tutor AI 24/7. Ini adalah bagian dari jalur belajar Tailwind CSS Academy, dan progresmu tersinkronisasi di web dan aplikasi CoddyKit. Kursus Tailwind CSS Academy mencakup 4 pelajaran total.
Bagian dari pelajaran ini belum diterjemahkan dan ditampilkan dalam bahasa Inggris.
What the Toggle Needs to Do
A dark mode toggle needs to accomplish three things: read the user's saved preference (or OS preference as a fallback), apply the correct class to the <html> element on page load, and update the class and save the preference when the user clicks the toggle button. Getting the initial load right is critical — applying the class before the page renders prevents a flash of incorrect theme.
Preventing Flash of Wrong Theme
The most common dark mode bug is a flash of light theme when a user in dark mode refreshes the page. This happens because JavaScript runs after the HTML has already been parsed and rendered. The fix is to run a tiny inline <script> in the <head> — before any CSS or body content — that reads localStorage and immediately adds the dark class if needed.
<!-- Place this FIRST inside <head> -->
<script>
if (localStorage.theme === 'dark' ||
(!('theme' in localStorage) && window.matchMedia('(prefers-color-scheme: dark)').matches)) {
document.documentElement.classList.add('dark');
}
</script>HTML Structure for the Toggle
The toggle button itself can be as simple as a <button> with sun and moon icons. Show the sun icon in dark mode (to switch to light) and the moon icon in light mode (to switch to dark). Use Tailwind's hidden and block with dark: variants to swap which icon is visible based on the current mode.
<button id="theme-toggle" class="p-2 rounded-lg bg-gray-200 dark:bg-gray-700">
<!-- Moon icon (visible in light mode) -->
<svg id="icon-moon" class="w-5 h-5 text-gray-800 dark:hidden" fill="currentColor" viewBox="0 0 20 20">
<path d="M17.293 13.293A8 8 0 016.707 2.707a8.001 8.001 0 1010.586 10.586z" />
</svg>
<!-- Sun icon (visible in dark mode) -->
<svg id="icon-sun" class="w-5 h-5 text-yellow-400 hidden dark:block" fill="currentColor" viewBox="0 0 20 20">
<path d="M10 2a1 1 0 100 2 1 1 0 000-2zm0 14a1 1 0 100 2 1 1 0 000-2z" />
</svg>
</button>Writing the Toggle JavaScript
The toggle function checks whether the dark class is currently present on <html>. If it is, the function removes it and saves 'light' to localStorage. If it is not, the function adds it and saves 'dark'. This pattern is clean, reversible, and works without any external libraries or frameworks.
const toggle = document.getElementById('theme-toggle');
toggle.addEventListener('click', () => {
const html = document.documentElement;
if (html.classList.contains('dark')) {
html.classList.remove('dark');
localStorage.setItem('theme', 'light');
} else {
html.classList.add('dark');
localStorage.setItem('theme', 'dark');
}
});Respecting OS Preference as Default
If the user has never interacted with your toggle, there is nothing in localStorage. In that case, you should fall back to the OS prefers-color-scheme media query. The window.matchMedia API lets you check this at runtime. If the OS is in dark mode and the user has not overridden it, apply the dark class so the initial experience matches their system setting.
function getInitialTheme() {
const saved = localStorage.getItem('theme');
if (saved) return saved;
// No saved preference — use OS setting
return window.matchMedia('(prefers-color-scheme: dark)').matches ? 'dark' : 'light';
}
if (getInitialTheme() === 'dark') {
document.documentElement.classList.add('dark');
}Full Toggle Implementation
Putting it all together: the inline head script handles initial load without flash, the button HTML uses dark: variants to swap icons, and the click handler toggles the class and saves to localStorage. This complete pattern is the standard approach used by most Tailwind-based apps. It requires no dependencies and works in any environment.
<!-- In <head> (anti-flash) -->
<script>
const saved = localStorage.getItem('theme');
const prefersDark = window.matchMedia('(prefers-color-scheme: dark)').matches;
if (saved === 'dark' || (!saved && prefersDark)) {
document.documentElement.classList.add('dark');
}
</script>
<!-- In body JS -->
<script>
document.getElementById('theme-toggle').addEventListener('click', () => {
const isDark = document.documentElement.classList.toggle('dark');
localStorage.setItem('theme', isDark ? 'dark' : 'light');
});
</script>Toggle Button With Smooth Transition
Add a satisfying animation to the theme switch by putting a transition-colors class on your body or root container. This makes all color changes animate smoothly instead of snapping instantly. Keep the transition duration short — around 200-300ms — to feel responsive. Apply it at the highest container level so all child elements inherit the smooth transition behavior.
<body class="bg-white dark:bg-gray-900 text-gray-900 dark:text-gray-100 transition-colors duration-200">
<!-- All children now transition smoothly between light and dark -->
</body>Toggle in a React Component
In React, manage the dark mode state with useState and synchronize it with the DOM and localStorage using useEffect. A common pattern is a custom useDarkMode hook that encapsulates all the logic. Trigger the DOM class change inside the effect so it stays in sync with the React state.
import { useState, useEffect } from 'react';
function useDarkMode() {
const [dark, setDark] = useState(() => localStorage.getItem('theme') === 'dark');
useEffect(() => {
document.documentElement.classList.toggle('dark', dark);
localStorage.setItem('theme', dark ? 'dark' : 'light');
}, [dark]);
return [dark, setDark];
}Toggle in a Next.js App
In Next.js, the anti-flash script cannot be easily placed in <head> via a component because React hydration runs after the HTML is parsed. The recommended approach is to add the inline script via next/script with strategy='beforeInteractive', or to place it directly in a custom _document.js file inside the Head component. This ensures the script runs synchronously before the page renders.
// pages/_document.js (Next.js Pages Router)
import { Html, Head, Main, NextScript } from 'next/document';
export default function Document() {
return (
<Html>
<Head>
<script dangerouslySetInnerHTML={{ __html: `
const t = localStorage.getItem('theme');
const d = window.matchMedia('(prefers-color-scheme: dark)').matches;
if (t === 'dark' || (!t && d)) document.documentElement.classList.add('dark');
` }} />
</Head>
<body><Main /><NextScript /></body>
</Html>
);
}Listening to OS Changes at Runtime
Users sometimes change their OS theme while your app is open. You can listen for these changes using window.matchMedia's change event. Only apply the OS preference change if the user has not set an explicit preference in your app — otherwise you would override their in-app choice. This provides the most respectful user experience.
const mediaQuery = window.matchMedia('(prefers-color-scheme: dark)');
mediaQuery.addEventListener('change', (e) => {
// Only auto-update if the user hasn't set an explicit preference
if (!localStorage.getItem('theme')) {
document.documentElement.classList.toggle('dark', e.matches);
}
});Toggle Accessibility Considerations
The dark mode toggle button should be keyboard accessible and have a meaningful aria-label that updates to reflect the current action. Use aria-pressed to communicate the current state to screen readers. Since only a visual icon changes, screen reader users need the label to understand what pressing the button will do.
<button
id="theme-toggle"
aria-label="Switch to dark mode"
aria-pressed="false"
class="p-2 rounded-lg bg-gray-200 dark:bg-gray-700"
>
<!-- icons -->
</button>
<script>
const btn = document.getElementById('theme-toggle');
btn.addEventListener('click', () => {
const isDark = document.documentElement.classList.toggle('dark');
btn.setAttribute('aria-pressed', isDark);
btn.setAttribute('aria-label', isDark ? 'Switch to light mode' : 'Switch to dark mode');
localStorage.setItem('theme', isDark ? 'dark' : 'light');
});
</script>Quick Check
Test your understanding of building a dark mode toggle with Tailwind CSS.
Lesson Recap
In this lesson you learned: an inline head script prevents the flash of wrong theme on page load, classList.toggle('dark') combined with localStorage creates a persistent user toggle, and matchMedia lets you respect the OS preference as a default when no user preference is saved. Next up we apply dark mode to complex components like cards, navbars, and modals.
Pertanyaan yang Sering Diajukan
Apakah pelajaran “Membangun Pengalih Mode Gelap” gratis?
Ya — teks lengkap “Membangun Pengalih Mode Gelap” gratis dibaca di sini di web. Untuk praktiknya secara interaktif (editor kode bawaan dan tutor AI 24/7) dan buka sisa kursus Tailwind CSS Academy, upgrade ke CoddyKit PRO. Kursus Tailwind CSS Academy mencakup 4 pelajaran total.
Apa yang akan aku pelajari di “Membangun Pengalih Mode Gelap”?
Implementasikan pengalih JavaScript yang menambahkan dan menghapus kelas dark pada elemen html serta menyimpan preferensi di localStorage. Kamu berlatih Tailwind CSS Academy dengan kode praktik yang langsung kamu jalankan di browser, dan tutor AI 24/7 menjawab pertanyaanmu saat kamu mengerjakan pelajaran ini.
Apakah aku perlu pengalaman untuk memulai Tailwind CSS Academy?
Tidak diperlukan pengalaman sebelumnya. Tailwind CSS Academy di CoddyKit dirancang untuk pemula hingga pelajar tingkat lanjut, jadi kamu bisa memulai di sini atau dari awal dan belajar sesuai kecepatan kamu sendiri. Ini adalah pelajaran 3 dari 4.
Berapa lama pelajaran “Membangun Pengalih Mode Gelap” memakan waktu?
Sebagian besar pelajaran CoddyKit memakan waktu sekitar 5–10 menit. Setiap pelajaran ringkas dan interaktif, jadi kamu membuat kemajuan stabil dan melanjutkan dari tempat kamu tinggalkan di web dan aplikasi.
Bisakah aku menulis dan menjalankan kode dalam pelajaran Tailwind CSS Academy ini?
Ya. Setiap pelajaran Tailwind CSS Academy menyertakan editor kode bawaan, jadi kamu menulis dan menjalankan kode nyata langsung di browser dan mendapatkan umpan balik AI instan — tidak diperlukan penyiapan lokal.
Semua pelajaran dalam kursus ini
- Strategi Mode Gelap
- Menerapkan Varian Gelap
- Membangun Pengalih Mode Gelap
- Mode Gelap untuk Komponen Kompleks