hyeondong-doctor-hd

You can diagnose Node.js and TypeScript dependencies by running a health scan that verifies runtime presence, package managers, tsconfig.json validity, and node_modules integrity, reporting structured issues for remediation.

A harness plugin dependency check covers runtime environment validation, project configuration files like package.json, code quality tools including ESLint and Prettier, test readiness, and build scripts to ensure deployment readiness.

Validate ESLint and Prettier configuration by scanning project settings to confirm tooling prerequisites, TypeScript compilation readiness via tsc, and test or e2e tooling setup, generating a structured report of any missing requirements.

Yes, you can check package.json and tsconfig.json health without a build by analyzing project settings, verifying scripts.build and scripts.dev existence, and validating configuration file structure independently of the compilation step.

Node.js project deployment may fail due to missing configuration such as an invalid .hyeondong-config.json, absent CLAUDE.md, incomplete node_modules, or missing build scripts, which a diagnostic scan identifies for remediation.

A specific Node.js version requirement depends on your harness plugin setup, but the diagnostic scan actively checks for Node.js presence and version compatibility alongside package manager determination to flag runtime issues.