steedos-validate-package

To validate a Steedos package structure, run `yarn validate` or `npx @steedos/validate` to check that package.json includes main: package.service.js and verifies packageLoader, namespace, and packageInfo. This ensures your package adheres to Steedos conventions before deployment.

The Steedos validator checks metadata files for objects, fields, triggers, functions, listviews, permissions, apps, and tabs. It enforces naming, type, and placement rules to ensure all metadata files follow the required structure and catch issues early.

Yes, you can generate a machine-readable JSON validation report for CI pipelines by running the validator with the `--json` option via `npx @steedos/validate --json`. This report surfaces structural errors early in your CI workflow.

Your Steedos package fails validation because the validator enforces required fields, naming conventions, and placement rules for metadata. It checks that package.json contains main: package.service.js and verifies packageLoader, namespace, and packageInfo are present.

The best way to lint Steedos package metadata is using the Steedos validator, which enforces naming, type, and placement rules across objects, fields, triggers, functions, listviews, permissions, apps, and tabs to catch compliance issues before deployment.

No specific dependencies are required to run Steedos package validation. You can execute the validator directly using `npx @steedos/validate` without installing additional packages, or add it to your project via `yarn validate`.