What is the purpose of the event-factories.ts in @ag-ui/core?

[SteffanEnnis]

I am in the process of migrating of a bespoke solution for handling events via websocket coming from our agentitc solution.

I have noticed that testing utilities are not exposed via the sdk packages. This makes sense because you don't want to bloat the package size of the run time code.

However this means for those who are working on a migration and need to impelmented unit tests/E2E tests such as myself. We cannot make use of the factories in the typescript sdk here https://github.com/ag-ui-protocol/ag-ui/blob/main/sdks/typescript/packages/core/src/event-factories.ts

I have also looked for instances these factories are being consumed outside of the event-factories.test.ts. I did not find any, I could be wrong here though.

I see three possible solutions

• Remove the factories from the code base because even though they are tested they do not serve a pragmatic purpose
• Pull them out of the @ag-ui/core package and place them in their own build tools package so that consumers can bring them in as a dev dependency
• Expose them in the index.ts file of @ag-ui/core so they are bundled with the main core package
  • Increasing the bundle size for testing utilities will have to be an accepted consequence.

[aniruddhaadak80]

I think your second option is the cleanest. Keeping those factories buried in core but unused outside tests makes them look like semi-public API surface without actually supporting consumers, and exporting them from runtime code feels like the wrong tradeoff if bundle size matters.nnA small dev-only package or test-utils export would make the intent much clearer. It also lets teams migrating onto AG-UI write realistic fixtures without having to copy internal helpers that may drift over time.