Building datafiles

Datafiles are static JSON inputs consumed by Eventvisor SDKs. A normal build generates one datafile for every Target.

npx eventvisor build

datafiles/
├── eventvisor-checkout.json
└── eventvisor-account.json

Targets keep related definitions together. Eventvisor includes definitions referenced by selected entities so the resulting datafile remains usable. This includes events and attributes that trigger selected effects. Explicit Target exclusions still win.

Reusable Schema references used by selected events and attributes are resolved and inlined. Schemas do not add a separate runtime collection to the datafile.

Selective builds#

npx eventvisor build --target checkout
npx eventvisor build --target checkout --target account
npx eventvisor build --target checkout --tag web

Tags remain entity selection metadata. They do not create artifacts by themselves. When both tag criteria and a Target definition apply, entities must satisfy both.

Print JSON#

npx eventvisor build --target checkout --json --pretty

Projects with Sets must pass one --set when printing JSON.

Revisions#

npx eventvisor build --revision 100
npx eventvisor build --revision-from-hash

Incremental revision state is stored under .eventvisor. Hash revisions are useful when unchanged content should keep the same cache key.