- Docs
- Help
- CLI / check
Docs for VelinStyle 1.3.x · verified against 1.3.0
CLI command fails or reports too much 1.3.0
Use the package-qualified CLI and narrow checks to the intended profile or severity. Deutsch
Problem
Commands 404, hang on huge trees, or flood the terminal with findings.
First check
Run the general diagnostic from the project directory first.
npx @birdapi/velinstyle doctor
Deeper check
npx @birdapi/velinstyle check . --profile app --json
npx @birdapi/velinstyle scan ./src --severity error
Quick check
- Run commands from the intended project directory.
- Use only documented profiles and flags.
- Check again after every change.
The CLI package cannot be found
Cause: Bare npx velinstyle resolves the wrong package and often returns 404.
- Solution 1: Always call
npx @birdapi/velinstyle <command>. - Solution 2: Start with
npx @birdapi/velinstyle doctor to confirm the local install. - Solution 3: Avoid inventing flags; use documented commands only.
Verify againnpx @birdapi/velinstyle doctor
npx @birdapi/velinstyle check ./index.html --profile docs
A check returns too many findings
Cause: The profile or target is broader than the page you meant to validate.
- Solution 1: Pick one profile:
marketing, app, docs, fragment, or ecommerce. - Solution 2: Prefer a single file for docs work:
check ./index.html --profile docs. - Solution 3: For scans, raise the floor with
--severity error on a focused path like ./src.
Verify againnpx @birdapi/velinstyle doctor
npx @birdapi/velinstyle check ./index.html --profile docs
VelinStyle