Files
agency/.pnpm-store/v3/files/d5/92c31d46b508f2ded376fd96a7a6212bc58a5e42dd846044621530b2d10243f4b45a14c89dc867c653404d0faa765d6b782bbb3ef9669b0d1d541b717ee8ba
hanzo-agent 5af6960b87 run project
Run: sess_f37640604ae254cb4d11dc6217f7b721
2026-09-30 00:04:56 +00:00

21 lines
1.1 KiB
Plaintext

/**
* The vocabulary, re-exported from where it is now defined.
*
* These names used to be declared here. They moved to @hanzo/events — the
* plural package is the catalog (many events, what each means, what each
* carries), this one is the client (one call sends one event). Splitting them
* that way is what lets the ingest endpoint read the same catalog: it is Go
* and cannot import TypeScript, so @hanzo/events also ships the data as JSON,
* and there is still exactly one definition.
*
* Nothing about the API moved. Every existing import keeps working, the names
* and their values are unchanged, and `pkgs/events/test/catalog.mjs` fails the
* build if a name and its meaning ever disagree.
*
* The naming convention lives with the names, in @hanzo/events and TAXONOMY.md:
* snake_case `<object>_<verb-past>`, a dimension is a PROPERTY and never part
* of the name, one name per user-visible moment shared by every surface.
*/
export { EVENTS, PAGEVIEW, EXCEPTION } from '@hanzo/events';
export type { EventName } from '@hanzo/events';
//# sourceMappingURL=events.d.ts.map