BootCheck

BootCheck is a lightweight VS Code extension that checks a project for common startup and setup problems using local, deterministic inspections.

Use

1. Open a project folder in VS Code.
2. Open the Command Palette (Ctrl+Shift+P / Cmd+Shift+P).
3. Run BootCheck: Diagnose Project.
4. Review the grouped Errors, Warnings, and Passed Checks in the results view.

To try a local build, package the extension and use the Extensions view's Install from VSIX... command to select the generated VSIX.

BootCheck only suggests commands. It does not install packages, run project scripts, edit files, or promise that a project will start.

Checks

• Detects package.json, pyproject.toml, requirements.txt, and Cargo.toml.
• Validates package JSON, TypeScript/JavaScript JSONC configurations, and Cargo/Python TOML manifests.
• Checks declared npm dependency folders, npm lockfile presence and selected lockfile consistency indicators, and a declared Node entry point.
• Statically scans JavaScript, TypeScript, Python, and Rust source for import, export, and require() references to external npm packages, then compares them against dependencies, devDependencies, optionalDependencies, and peerDependencies in package.json. Imported packages not declared in the manifest are reported as an inconclusive warning. Node.js built-ins, relative imports, absolute imports, type-only imports, and package subpaths are excluded.
• Compares environment-variable names found in JavaScript, TypeScript, Python, and Rust source with safe templates named .env.example, .env.template, .env.sample, or .env.defaults.
• Checks whether npm, Python, or Cargo can be found on PATH when the corresponding manifest is present.
• Reports unreadable files, unsupported projects, and bounded or incomplete scans as inconclusive rather than claiming a project is broken.

Static source checks are intentionally conservative. Import analysis cannot resolve dynamically constructed imports (e.g. require(x)), multiline import statements where from is on a different line, or inline type modifiers beyond import type and import { type X }. Environment-variable references built dynamically, TOML/lockfile compatibility beyond the checks above, native toolchains, and project-specific runtime behavior are not verified.

Privacy and safety

All diagnostics run locally. BootCheck has no AI or network service and does not execute package scripts or other project-controlled commands. It never opens real .env files. Safe environment templates are read only to collect variable names before =; values are neither retained nor displayed. Source inspection is bounded by file size, total bytes, and a configurable maximum number of files (bootcheck.maxSourceFiles).

Troubleshooting

• An inconclusive result means BootCheck could not inspect enough information to make a reliable claim; check file permissions and scan-limit warnings.
• A missing-tool warning means the executable was not found on PATH, not that the project cannot start.
• For multiple-root workspaces, BootCheck checks each open folder and labels findings by folder.
• Run BootCheck: Diagnose Project again after changing setup files.

Development and release

Requirements: Node.js 22 or newer and npm. Install development dependencies with npm install, then run npm run verify.

npm run package runs lint, automated tests, TypeScript compilation, and release checks before creating bootcheck-0.0.2.vsix. node scripts/verify-release.cjs --vsix bootcheck-0.0.2.vsix verifies the embedded manifest and package contents.

For each future release, update the version in package.json (the sole version source), update CHANGELOG.md, and rerun npm run package. VSCE derives the VSIX filename from the manifest version; never edit a generated VSIX manifest. Replace the initial publisher-placeholder only with an authorized Marketplace publisher ID before publishing.

License

MIT. See the LICENSE file included in this distribution.