KO | EN

GitLite

Minimalist Open Source Repository Search Engine

gitlite — search

#developer-tools #typescript #claude-code #codex #dsh #dsh-plugin #ai-agent #ai-agents #deepseek-harness #agent-skills #macos #cli

use-prefers-color-scheme

★ 32 Open GitHub ↗

🪝 React hook for subscribing to user's color scheme preference.

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

<br>

<br>

<h1 align="center">use-prefers-color-scheme</h1>
<h3 align="center"><a href="https://reactjs.org">React</a> hook for subscribing to user's color scheme preference.</h3>

<br>

<br>

## 🚀 Getting Started

### 🐇 Jump Start

```shell
npm install @anatoliygatt/use-prefers-color-scheme
```

```jsx
import { usePrefersColorScheme } from '@anatoliygatt/use-prefers-color-scheme';

### 💻 Live Demo

[![Open in CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/s/demo-for-anatoliygatt-use-prefers-color-scheme-llkul)

## ⚙️ Usage with Server Side Rendering (SSR)

Frameworks like Next.js and Gatsby take advantage of server-side rendering, which means that the HTML is pre-rendered at some point before it's sent to the browser. When we first render our React component tree, we don't know whether the user prefers light or dark color scheme.

It may lead to the markup mismatches during hydration. In order to prevent this, we need to set the `ssr` option provided by the `usePrefersColorScheme()` hook to `true`, like so:

```javascript
usePrefersColorScheme({ ssr: true });
```

This will guarantee no markup mismatches between the original server render and the first client render, however, we will have to make a compromise: force a dark color scheme for **_all users_** in the very first render.

## 👨🏼‍⚖️ License

[MIT](https://github.com/anatoliygatt/use-prefers-color-scheme/blob/master/LICENSE)

use-prefers-color-scheme

Explore Similar Repositories

Was this content helpful?

Recent Feedback

Download README