|
|
2 months ago | |
|---|---|---|
| .. | ||
| README.md | 2 months ago | |
| auto-detect-components.sh | 2 months ago | |
| check-dependencies.ts | 2 months ago | |
| fix-registry.py | 2 months ago | |
| register-component.sh | 4 months ago | |
| validate-component.sh | 2 months ago | |
| validate-profile-coverage.sh | 2 months ago | |
| validate-registry.sh | 2 months ago | |
| validate-registry.ts | 2 months ago | |
This directory contains scripts to validate the registry.json file.
Fast, modern, and easy to debug
# Run validation
npm run validate:registry
# Run with verbose output
npm run validate:registry:verbose
# Run with fix suggestions
npm run validate:registry:fix
# Or run directly with bun
bun run scripts/registry/validate-registry.ts
bun run scripts/registry/validate-registry.ts -v
bun run scripts/registry/validate-registry.ts -f
Requirements:
Features:
Original bash script - still maintained for CI compatibility
# Run validation
./scripts/registry/validate-registry.sh
# Run with verbose output
./scripts/registry/validate-registry.sh -v
# Run with fix suggestions
./scripts/registry/validate-registry.sh -f
Requirements:
Note: The bash version may hang in some CI environments. The TypeScript version is recommended for local development.
Both scripts validate:
registry.json is valid JSON0 - All paths valid, all dependencies valid1 - Missing files or missing dependencies found2 - Registry parse error or missing script dependenciesThe GitHub Actions workflow (.github/workflows/validate-registry.yml) currently uses the bash version for compatibility with the base branch workflow file. Once this PR is merged, future PRs can use the TypeScript version.
To modify the TypeScript validator:
scripts/registry/validate-registry.tsnpm run validate:registryThe TypeScript version is the source of truth for new features.