shadow-cljs-debug

Diagnose shadow-cljs compilation and interop errors in ClojureScript projects.

6|Updated Mar 11, 2026

Search Tags:#debugging #configuration #clojurescript #interop #build-errors #dependency-resolution #shadow-cljs

Ready to run

npx skills add https://github.com/open-hax/opencode-skills --skill shadow-cljs-debug

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: shadow-cljs-debug
Source: https://github.com/open-hax/opencode-skills/tree/main/.opencode/skills/shadow-cljs-debug
Command: npx skills add https://github.com/open-hax/opencode-skills --skill shadow-cljs-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Shadow-CLJS debugging can be opaque, with errors that stem from mismatched configs, missing dependencies, or interop issues. This guide provides a structured approach to diagnose and resolve common Shadow-CLJS compilation problems.

Core Features & Use Cases

Error analysis: differentiate between compilation errors, dependency issues, and interop problems.
Config verification: inspect shadow-cljs.edn, deps.edn, and package.json for correct build IDs and paths.
Recovery steps: clear caches, restart watchers, and re-run builds to validate fixes.
Interop checks: confirm npm package requires and JS interop conventions.

Quick Start

Run a failing Shadow-CLJS build, review the error details, then follow the steps to identify and fix configuration or dependency issues.

Frequently Asked Questions about shadow-cljs-debug

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I fix shadow-cljs build errors like Undeclared Var or No such namespace?▼

To fix shadow-cljs build errors like Undeclared Var, inspect shadow-cljs.edn, deps.edn, and package.json for correct build IDs and paths, then clear caches and re-run the build.

What causes Analysis Error during ClojureScript compilation with shadow-cljs?▼

An Analysis Error during ClojureScript compilation is caused by mismatched configurations, missing dependencies, or JS interop issues, requiring inspection of package.json and shadow-cljs.edn.

How do I verify npm dependencies and JS interop in a shadow-cljs project?▼

Verify npm dependencies and JS interop in shadow-cljs by inspecting package.json requires, confirming JS interop conventions, clearing caches, and re-running the build to validate fixes.

Does this shadow-cljs debugging approach work with deps.edn configurations?▼

Yes, this shadow-cljs debugging approach works with deps.edn configurations by inspecting deps.edn alongside shadow-cljs.edn and package.json to identify mismatched paths and dependency issues.

Why does my shadow-cljs build fail after adding new npm packages?▼

Your shadow-cljs build fails after adding new npm packages due to dependency resolution issues or missing requires, requiring package.json inspection, cache cleanup, and a watcher restart.

What is the best way to clear shadow-cljs caches to resolve compilation issues?▼

The best way to clear shadow-cljs caches to resolve compilation issues is to perform a cache cleanup, restart the build watchers, and re-run the build to verify the errors are resolved.