// the find
folke/tokyonight.nvim
🏙 A clean, dark Neovim theme written in Lua, with support for lsp, treesitter and lots of plugins. Includes additional themes for Kitty, Alacritty, iTerm and Fish.
Tokyo Night is a Neovim colorscheme ported from the VS Code theme of the same name, offering four variants (storm, moon, night, day) with Lua-based configuration. It's for Neovim users who want deep plugin integration out of the box — LSP, treesitter, and a long list of popular plugins are all covered. The extras system extends the palette to terminals, shells, and other tools so your whole environment matches.
The plugin coverage is genuinely thorough — 60+ plugins each get their own highlight group file rather than a catch-all approximation, so things like blink.cmp, bufferline, and noice actually look intentional rather than accidentally readable. The on_colors/on_highlights escape hatches are clean: you get the full color table and can override at any granularity without forking the theme. The extras generator is a smart architectural choice — color configs for Kitty, Alacritty, WezTerm, lazygit, delta and 40 others are derived from the same Lua palette, so they stay in sync when the palette changes. The cache layer (compiled highlight tables written to disk) means theme load time is negligible after first use.
Four style variants sounds like flexibility but in practice moon and storm are close enough that most users just pick one and forget the others exist — the day variant is the outlier that actually earns its keep. The auto-detection of which plugin highlights to load (via lazy.nvim integration) is clever but adds an invisible dependency: if you're not on lazy, you have to manually enumerate plugins in config, which isn't obvious from the README. The extras files are generated artifacts checked into the repo, which means PRs that add a new extra touch dozens of files and the generation script isn't surfaced prominently for contributors. No built-in contrast checker or accessibility tooling — the palette looks good on the author's screen but there's no guarantee it meets WCAG minimums for users with different displays or vision needs.