CSS Peek not working at all

[Solomin0]

No shortcuts or popups are working. I just tried to download it and im getting nothing.
I try to ctrl hover a class and no highlighting either.

[someramsey]

I am having the same problem. I have even tried running it without other extensions. It still doesn't work.

[raed-husseini]

same here. CSS Peek 4.4.1 on vscode 1.89.1 on windows 11.

[pranaygp]

Thanks for the report. I took a fresh look at the activation flow for this issue and can't find an obvious bug from the codebase alone — the LSP path, document selectors, and the peekFromLanguages plumbing all look correct. To move forward I need some specifics from anyone still hitting this.

What I checked

• Activation events (package.json): the extension activates via workspaceContains:**/*.{css,scss,sass,less} — so if the workspace has zero stylesheet files of those types in any subdirectory, the extension never activates.
• Client document selector (client/src/extension.ts): built from cssPeek.peekFromLanguages plus the built-in stylesheet languages, and passed both as the LanguageClient documentSelector and as initializationOptions.peekFromLanguages to the server.
• Server peek gate (server/src/server.ts): onDefinition gates on settings.peekFromLanguages.includes(document.languageId). If your file's language ID isn't in the list, peek will silently no-op.
• Stylesheet discovery (client/src/extension.ts): Workspace.findFiles runs against **/*.{css,scss,less} minus cssPeek.peekToExclude. If this returns zero files, the LSP starts with an empty stylesheet map and no definitions will ever resolve.

Most likely causes, ranked

1. Workspace has no .css/.scss/.sass/.less files at activation time — extension never activates. Common in monorepos where styles live outside the opened folder, or projects that use only CSS-in-JS / Tailwind utility classes with no actual stylesheet files.
2. File's language ID isn't in cssPeek.peekFromLanguages — e.g. astro, liquid, or a Vue/JSX file that some other extension has remapped to a custom language ID. The server's onDefinition returns null immediately in that case.
3. All stylesheets matched by cssPeek.peekToExclude — defaults exclude node_modules and bower_components, but a custom exclude pattern could swallow everything.
4. Stylesheet files exist but the class/id genuinely isn't defined in any of them — the screenshot in the OP shows what looks like a Tailwind class (bg-cyan-50); those won't be peekable since they aren't declared in user stylesheets.

Info I need to act on this

If you (OP or anyone else still seeing this on the latest VSCode + CSS Peek 4.4.3) can provide:

1. Are you still seeing this on the latest VSCode (1.95+) and CSS Peek 4.4.3? The original report is from VSCode 1.89 in May 2024, and several pieces have changed since then.
2. Verbose server log — set "cssPeek.trace.server": "verbose" in settings.json, reload the window, open your HTML/JSX/etc. file, attempt a peek, then paste the contents of Output → CSS Peek. In particular the line Number of style sheets - N tells us whether any stylesheets were discovered at all.
3. Exact language ID of the file you're peeking from — bottom-right of the VSCode status bar, or Cmd/Ctrl+Shift+P → Change Language Mode.
4. Your cssPeek.peekFromLanguages and cssPeek.peekToExclude settings (defaults are fine, but please confirm you haven't overridden them).
5. A minimal repro — a tiny folder with one stylesheet and one consuming file would let me confirm or rule this out quickly.

Without those I can't act on this, so I'll leave it open for now but it's a candidate to close as stale if no info comes in.